Enhanced Claims Damage Estimation Using Aggregate Display

ABSTRACT

Systems and methods provide for an automated system for analyzing damage to process claims associated with an insured item, such as a vehicle. An enhanced claims processing server may analyze damage associated with the insured item using photos/video transmitted to the server from a user device (e.g., a mobile device). The enhanced claims processing server may submit a signal that locks one or more portions of an application on the mobile device used to submit the photos/videos. The mobile device may receive feedback from the server regarding the acceptability of submitted photos/video. The photos may further be annotated using, for example, a touch screen display. An estimate, such as a cost estimate, may be determined for the damage associated with the insured item based on the photos and/or annotations.

CROSS-REFERENCE TO RELATED-APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/190,976 filed Feb. 26, 2014, which is a continuation of U.S.application Ser. No. 14/076,435 filed Nov. 11, 2013, and entitled“Enhanced Claims Damage Estimation Using Aggregate Display,” now U.S.Pat. No. 8,712,893, which is a continuation-in-part of U.S. applicationSer. No. 13/834,161 filed on Mar. 15, 2013, and entitled“Agent-Facilitated Claims Damage Estimation,” which is acontinuation-in-part of U.S. application Ser. No. 13/587,620 filed onAug. 16, 2012, and entitled “Feedback Loop in Mobile Damage Assessmentand Claims Processing,” now U.S. Pat. No. 8,510,196. U.S. applicationSer. No. 13/834,161 is also a continuation-in-part of U.S. applicationSer. No. 13/587,630 filed on Aug. 16, 2012, and entitled “UserInteractions in Mobile Damage Assessment and Claims Processing.” U.S.application Ser. No. 13/834,161 is also a continuation-in-part of U.S.application Ser. No. 13/587,635 filed on Aug. 16, 2012, and entitled“Processing Insured Items Holistically with Mobile Damage Assessment andClaims Processing.” The disclosures of each of these priorityapplications are hereby incorporated by reference in their entirety.This application is related to U.S. application Ser. No. 13/834,170filed on Mar. 15, 2013, entitled “Pre-Claim Consultations,” U.S.application Ser. No. 13/834,193 filed on Mar. 15, 2013, entitled “ThirdParty Pre-Claim Consultations,” and U.S. application Ser. No. 13/834,210filed on Mar. 15, 2013, entitled “User Devices in Claims DamageEstimation,” the disclosures of which are hereby incorporated byreference in their entirety. This application is also related to U.S.application Ser. No. 14/076,473 filed on Nov. 11, 2013, entitled“Enhanced Claims Damage Estimation Using Dynamic Display,” thedisclosure of which is hereby incorporated by reference in its entirety.

TECHNICAL FIELD

The present disclosure relates to systems and methods for analyzingdamage to an item for insurance purposes.

BACKGROUND

Conventional insurance claims processing is a complex process thatstarts with a first notification of loss related to an insured item.Upon notification of loss, the claim may be routed to multiple claimsadjusters that analyze different aspects of the damage associated withthe insured item in order to determine whether compensation for the lossis appropriate.

In general, conventional claims adjustment can involve paperworkprocessing, telephone calls, and potentially face-to-face meetingsbetween claimant and adjuster. In addition, a significant amount of timecan elapse between a first notice of loss from the claimant and thefinal settlement of the claim.

In addition, while consumers may take advantage of conventional claimsprocessing to determine if they will receive any compensation for lossassociated with an item, consumers have traditionally had very fewoptions for obtaining advice associated with loss prior to submission ofan insurance claim. Moreover, traditional claims processing oftenrequires multiple actors sharing numerous documents. Accordingly, theremay be a need for efficient claims processing to better serve customers.

SUMMARY

The following presents a simplified summary of the present disclosure inorder to provide a basic understanding of some aspects of thedisclosure. This summary is not an extensive overview of the disclosure.It is not intended to identify key or critical elements of thedisclosure or to delineate the scope of the disclosure. The followingsummary merely presents some concepts of the disclosure in a simplifiedform as a prelude to the more detailed description provided below.

Aspects of the disclosure involve a streamlined and efficient processfor claims management and disclose methods, computer-readable media, andapparatuses for automating the processing and settling of claims relatedto an insured item. A mobile device may transmit data (e.g., images,video, etc.) related to damage associated with an insured item to anenhanced claims processing server. The enhanced claims processing servermay manage analysis of damage associated with the insured item andsettlement of a claim related to the damage.

In another aspect of the disclosure, an application stored on the mobiledevice may be used to capture the data related to the damage. Once themobile device transmits the captured data, for instance as a part of aclaim submission, one or more portions of the application used tocapture the data may be locked.

In another aspect of the disclosure, the enhanced claims processingserver may send one or more messages to the mobile device that instructa user to capture additional data related to the damage. One or moreportions of the application used to capture data may be unlocked suchthat the user may capture additional data in accordance with theinstructions.

Aspects of the disclosure also involve receiving data about an insureditem, such as photos of a vehicle, and annotating the received data. Inan embodiment, damage annotations may be added to received photos thatindicate, for example, a type and a severity for damage displayed in thephotos. One or more interfaces, such as a lens, may be displayed to auser such that the interfaces adjust the display of the received photos.In an example, a touch screen display may be used to generate one ormore annotations.

Aspects of the disclosure also involve receiving data about an insureditem, such as photos of a vehicle, receiving annotations associated withthe received data, and determining an estimate based on the receiveddata. In an embodiment, received photos and/or received damageannotations may be used to determine one or more parts of an insureditem for repairing or replacing. Based on the determined parts, a costmay be calculated for the estimate.

Further aspects of the disclosure may be provided in a computer-readablemedium having computer-executable instructions that, when executed,cause a computer, user terminal, or other apparatus to at least performone or more of the processes described herein.

BRIEF DESCRIPTION OF THE DRAWINGS

All descriptions are exemplary and explanatory only and are not intendedto restrict the disclosure, as claimed. The accompanying drawings, whichare incorporated in and constitute a part of this specification,illustrate embodiments of the disclosure and, together with thedescription, serve to explain the principles of the disclosure. In thedrawings:

FIG. 1 shows an illustrative operating environment in which variousaspects of the disclosure may be implemented.

FIG. 2 shows a system of network devices and servers that may be used toimplement the processes and functions of certain aspects of the presentdisclosure.

FIG. 3 shows a flow chart for an automated damage assessment process inaccordance with certain aspects of the present disclosure.

FIG. 4 shows a series of initial display screens displayed when a userstarts a damage assessment and claims processing application stored on amobile device in accordance with certain aspects of the presentdisclosure.

FIG. 5a shows a first series of display screens displayed on a mobiledevice as a user takes photos of a damaged vehicle in accordance withcertain aspects of the present disclosure.

FIG. 5b shows a second series of display screens displayed on a mobiledevice as a user takes photos of a damaged vehicle in accordance withcertain aspects of the present disclosure.

FIG. 6 shows a series of display screens displayed on a mobile devicefor enabling a user to delete photos that have already been taken inaccordance with certain aspects of the present disclosure.

FIG. 7 shows a series of display screens displayed on a mobile devicefor enabling a user to submit photos for review by an enhanced claimsprocessing server, in accordance with certain aspects of the presentdisclosure.

FIG. 8 shows a series of display screens displayed on a mobile devicefor enabling a user to receive feedback from an enhanced claimsprocessing server regarding previously submitted photos, in accordancewith certain aspects of the present disclosure.

FIG. 9 shows a flow chart for providing pre-claim consultations inaccordance with certain aspects of the present disclosure.

FIG. 10 shows a flow chart for providing pre-claim consultations with athird party entity in accordance with certain aspects of the presentdisclosure.

FIG. 11 shows a flow chart for using a user device to allow a thirdparty entity to learn about damage to an insured item while the damageis still being assessed through a claims adjustment process inaccordance with certain aspects of the present disclosure.

FIG. 12 shows a login screen displayed on a user device in accordancewith certain aspects of the present disclosure.

FIG. 13 shows two display screens displayed on a user device that allowa user to capture damage information associated with a new claim and/oraccess information related to claims that have been previously submittedfor claims adjustment, in accordance with certain aspects of the presentdisclosure.

FIG. 14 shows two display screens displayed on a user device fordisplaying messages associated with a given claim, in accordance withcertain aspects of the present disclosure.

FIG. 15 shows a first set of two display screens displayed on a userdevice for providing user instructions for capturing images related todamage associated with an insured item, in accordance with certainaspects of the present disclosure.

FIG. 16 shows two display screens that display images of damage beingcaptured by a user device, in accordance with certain aspects of thepresent disclosure.

FIG. 17 shows a second set of two display screens displayed on a userdevice for providing user instructions for capturing images related todamage associated with an insured item, in accordance with certainaspects of the present disclosure.

FIG. 18 shows a display screen with visual aids for aiding a user inproperly positioning an imaging device associated with a user device tocapture images related to damage of an insured item, in accordance withcertain aspects of the present disclosure.

FIG. 19 shows two display screens displayed on a user device fordisplaying instructions related to capturing images for processing aclaim associated with damage of an insured item, in accordance withcertain aspects of the present disclosure.

FIG. 20 shows two display screens displayed on a user device forreviewing images depicting damage to an insured item, as captured by animaging device, in accordance with certain aspects of the presentdisclosure.

FIG. 21 shows a display screen displayed on a user device for displayingclaim information associated with damage to an insured item, inaccordance with certain aspects of the present disclosure.

FIG. 22 shows a flow chart for an automated damage assessment process ona mobile device in accordance with certain aspects of the presentdisclosure.

FIG. 23 shows a display screen with claim estimates for a user inaccordance with certain aspects of the present disclosure.

FIG. 24 shows a display screen with multiple stages that enable a userto submit a damage claim, in accordance with certain aspects of thepresent disclosure.

FIG. 25 shows multiple display screens displayed on a user device forproviding user instructions for capturing images related to damageassociated with an insured item at a first stage, in accordance withcertain aspects of the present disclosure.

FIG. 26 shows multiple display screens displayed on a user device forproviding user instructions for capturing images related to damageassociated with an insured item at a second stage, in accordance withcertain aspects of the present disclosure.

FIG. 27 shows a display screen with visual aids for aiding a user inproperly positioning an imaging device associated with a user device tocapture images related to damage of an insured item, in accordance withcertain aspects of the present disclosure.

FIG. 28 shows multiple display screens displayed on a user device forproviding user instructions for capturing images related to damageassociated with an insured item at a third stage, in accordance withcertain aspects of the present disclosure.

FIG. 29 shows a display screen displayed on a user device for providinguser instructions for inputting data related to a claim associated withan insured item at a fourth stage, in accordance with certain aspects ofthe present disclosure.

FIG. 30 shows a display screen displayed on a user device for submittinga claim associated with an insured item, in accordance with certainaspects of the present disclosure.

FIG. 31 shows multiple display screens displayed on a user device fordisplaying a message to a user about a submitted claim, in accordancewith certain aspects of the present disclosure.

FIG. 32 shows a flow chart for displaying and annotating received datain accordance with certain aspects of the present disclosure.

FIG. 33 shows a display screen for displaying and annotating receiveddata in accordance with certain aspects of the present disclosure.

FIG. 34 shows multiple display screens for generating an annotationabout damage to an insured item in accordance with certain aspects ofthe present disclosure.

FIG. 35 shows multiple display screens for generating an annotationabout damage to an insured item using a drag motion in accordance withcertain aspects of the present disclosure.

FIGS. 36 and 37 show display screens for displaying received data anddisplaying annotations describing the received data in accordance withcertain aspects of the present disclosure.

FIG. 38 shows a display screen for adjusting the display of receiveddata using an interface in accordance with certain aspects of thepresent disclosure.

FIG. 39 shows a display screen for adjusting the display of receiveddata using multiple interfaces in accordance with certain aspects of thepresent disclosure.

FIG. 40 shows an interface used to adjust the display of received datain accordance with certain aspects of the present disclosure.

FIG. 41 shows a display screen for configuring an interface used toadjust the display of received data in accordance with certain aspectsof the present disclosure.

FIG. 42 shows a flow chart for displaying received data about an insureditem and determining an estimate for the insured item in accordance withcertain aspects of the present disclosure.

FIG. 43 shows a display screen for displaying received data and receivedannotations about the received data in accordance with certain aspectsof the present disclosure.

FIG. 44 shows a display screen for receiving part information about adamaged part of an insured item in accordance with certain aspects ofthe present disclosure.

FIG. 45 shows a display screen for determining a cost estimate forreplacing or repairing a damaged part of an insured item in accordancewith certain aspects of the present disclosure.

FIG. 46 shows a flow chart for displaying received data about an insureditem and determining an estimate for the insured item in accordance withcertain aspects of the present disclosure.

FIG. 47 shows a display screen for displaying received photos andreceived data in accordance with certain aspects of the presentdisclosure.

FIG. 48 shows a display screen for annotating received data inaccordance with certain aspects of the present disclosure.

FIG. 49 shows a display screen for displaying a cost estimate for aninsured item in accordance with certain aspects of the presentdisclosure.

FIG. 50 shows a display screen for displaying a cost estimate for aninsured item based on annotations in accordance with certain aspects ofthe present disclosure.

FIG. 51 shows a display screen for displaying a plurality of costestimates for an insured item based on annotations in accordance withcertain aspects of the present disclosure.

FIG. 52 shows a display screen for displaying a cost estimate for aninsured item based on annotations in accordance with certain aspects ofthe present disclosure.

DETAILED DESCRIPTION

In accordance with various aspects of the disclosure, methods,computer-readable media, and apparatuses are disclosed through whichinsurance claims may be settled through an enhanced automated process.In certain aspects, when an enhanced claims processing server receivesdata regarding an insured item (e.g., a vehicle, etc.) from a computingdevice (e.g., a mobile device), the server processes the data andmanages settlement of a claim associated with the insured item.

The automated process may utilize various hardware components (e.g.,processors, communication servers, memory devices, sensors, etc.) andrelated computer algorithms to generate image data related to damageassociated with an insured item, determine if the image data conforms toa predetermined set of criteria, analyze the image data to assess lossassociated with the insured item, and determine if a payment isappropriate to the claimant as compensation for assessed loss.

FIG. 1 illustrates a block diagram of an enhanced claims processingserver 101 (e.g., a computer server) in communication system 100 thatmay be used according to an illustrative embodiment of the disclosure.The server 101 may have a processor 103 for controlling overalloperation of the enhanced claims processing server 101 and itsassociated components, including RAM 105, ROM 107, input/output module109, and memory 115.

I/O 109 may include a microphone, keypad, touch screen, and/or stylusthrough which a user of enhanced claims processing server 101 mayprovide input, and may also include one or more of a speaker forproviding audio output and a video display device for providing textual,audiovisual, and/or graphical output. Software may be stored withinmemory 115 to provide instructions to processor 103 for enabling device101 to perform various functions. For example, memory 115 may storesoftware used by the device 101, such as an operating system 117,application programs 119, and an associated database 121. Processor 103and its associated components may allow the device 101 to run a seriesof computer-readable instructions to analyze image data depicting damageto an insured item (e.g., vehicle, etc.). Processor 103 may determinethe general location of damage associated with the vehicle by analyzingimages of the vehicle and comparing these images with reference imagesof a similar vehicle with no damage or with similar damage. In addition,processor 103 may assess the loss associated with the damaged vehicleand transmit terms for settling an insurance claim related to the lossto a user of a mobile device.

The server 101 may operate in a networked environment supportingconnections to one or more remote computers, such as terminals 141 and151. The terminals 141 and 151 may be personal computers or servers thatinclude many or all of the elements described above relative to theserver 101. Also, terminal 141 and/or 151 may be data stores for storingimage data of insured items that have been analyzed by the enhancedclaims processing server 101 in the past. In yet other embodiments,terminals 141 and 151 may represent mobile devices with built-in camerasfor capturing image data associated with a damaged item.

The network connections depicted in FIG. 1 include a local area network(LAN) 125 and a wide area network (WAN) 129, but may also include othernetworks. When used in a LAN networking environment, the server 101 isconnected to the LAN 125 through a network interface or adapter 123.When used in a WAN networking environment, the server 101 may include amodem 127 or other means for establishing communications over the WAN129, such as the Internet 131. It will be appreciated that the networkconnections shown are illustrative and other means of establishing acommunications link between the computers may be used. The existence ofany of various well-known protocols such as TCP/IP, Ethernet, FTP, HTTPand the like is presumed.

Additionally, an application program 119 used by the enhanced claimsprocessing server 101 according to an illustrative embodiment of thedisclosure may include computer executable instructions for invokingfunctionality related to calculating an appropriate payment for assesseddamage associated with an insured item.

Enhanced claims processing server 101 and/or terminals 141 or 151 mayalso be mobile terminals including various other components, such as abattery, speaker, camera, and antennas (not shown).

The disclosure is operational with numerous other general purpose orspecial purpose computing system environments or configurations.Examples of well known computing systems, environments, and/orconfigurations that may be suitable for use with the disclosure include,but are not limited to, personal computers, server computers, hand-heldor laptop devices, multiprocessor systems, microprocessor-based systems,set top boxes, programmable consumer electronics, network PCs,minicomputers, mainframe computers, and distributed computingenvironments that include any of the above systems or devices, and thelike.

The disclosure may be described in the general context ofcomputer-executable instructions, such as program modules, beingexecuted by a computer. Generally, program modules include routines,programs, objects, components, data structures, etc. that performparticular tasks or implement particular abstract data types. Thedisclosure may also be practiced in distributed computing environmentswhere tasks are performed by remote processing devices that are linkedthrough a communications network. In a distributed computingenvironment, program modules may be located in both local and remotecomputer storage media including non-transitory memory storage devices,such as a hard disk, random access memory (RAM), and read only memory(ROM).

Referring to FIG. 2, a system 200 for implementing methods according tothe present disclosure is shown. As illustrated, system 200 may includeone or more network devices 201. Devices 201 may be local or remote, andare connected by one or more communications links 202 to computernetwork 203 that is linked via communications links 205 to enhancedclaims processing server 101. In certain embodiments, network devices201 may run different algorithms used by server 101 for analyzing imagedata showing damage associated with an insured item, or, in otherembodiments, network devices 201 may be data stores for storingreference image data of insured items. In yet other embodiments, networkdevices 201 may represent mobile user devices configured to captureimage data (e.g., via a camera, etc.) associated with a damaged insureditem and to transmit the image data to server 101. In system 200,enhanced claims processing server 101 may be any suitable server,processor, computer, or data processing device, or combination of thesame.

Computer network 203 may be any suitable computer network including theInternet, an intranet, a wide-area network (WAN), a local-area network(LAN), a wireless network, a digital subscriber line (DSL) network, aframe relay network, an asynchronous transfer mode (ATM) network, avirtual private network (VPN), or any combination of any of the same.Communications links 202 and 205 may be any communications linkssuitable for communicating between network devices 201 and server 101,such as network links, dial-up links, wireless links, hard-wired links,etc.

The steps that follow in the Figures may be implemented by one or moreof the components in FIGS. 1 and 2 and/or other components, includingother computing devices.

In accordance with aspects of the disclosure, a user (e.g., a claimant)of a mobile device (e.g., mobile phone, personal digital assistant(PDA), etc.) may take a variety of photos associated with damage to aninsured vehicle. The photos may include wide shots of the damagedvehicle, pictures of an identification number associated with thedamaged vehicle (e.g., a vehicle identification number (VIN), etc.),current odometer reading, and/or multiple angles/close-up shots of thedamage associated with the insured vehicle.

Once the user is satisfied that the appropriate photos have been taken,the user may transmit the photos to an enhanced claims processing server101. The enhanced claims processing server 101 may be configured toreceive and analyze the photos to determine if they meet a predefinedset of criteria (e.g., not too blurry, correct angles, etc.) forcompleteness, accuracy, etc. If the photos do not meet the minimumcriteria, server 101 may transmit a message (e.g., via a feedback loop),informing the mobile device that alternative and/or additional photosmust be taken. This process of assuring that the photos are compliantfor further analysis may be repeated until the user of device 201 hascomplied with all of the rules set forth by enhanced claims processingserver 101. Server 101 may then analyze the photos to generate anoutput, including a cost estimate to repair the damage associated withthe insured vehicle and/or to replace a damaged part of the insuredvehicle. In some aspects, to generate this output, server 101 mayanalyze the photos and determine the location of damage (e.g., exteriorparts, etc.), extent of damage, and/or the cost of parts/labor to fixthe damage.

In some instances, depending on the amount of damage to the insuredvehicle, the cost estimate may represent the cost of replacing theinsured vehicle itself. Along with the cost estimate forrepair/replacement of the insured vehicle, server 101 may also outputvarious claims documents, including disclosures, brochures, guarantees,etc. If appropriate, server 101 may transmit a payment to the userand/or to an account associated with the user, for the cost of repairingthe damage or replacing a part. In addition, server 101 may inform theuser approximately how long it will take to repair/replace the insuredvehicle.

In some aspects, damage inspection and appraisal in the automated claimsprocessing scheme discussed herein may be completed in thirty minutes orless.

Although embodiments of the disclosure discussed herein relate to aninsured vehicle analyzed by enhanced claims processing server 101, oneof ordinary skill in the art would recognize that other types of insureditems, including homes, may be employed with a similar scheme.

In certain aspects, the use of server 101 may aid in cutting down timebetween a first notice of loss and settlement of the claim (e.g.,real-time settlement of a claim) associated with the loss (e.g., via apayment and/or information regarding repair/replacement of an insureditem). In addition, because the methods discussed herein are automatedand allow claims adjusters to inspect damages remotely or reduce theinvolvement of claims adjusters, less time and money may be spent totransport these adjusters to inspection locations. The automated natureof this process may also create the opportunity for remote humaninspections of damage associated with insured items.

Also, the technologies used in the claims adjustment processesimplemented by server 101 may aid in attracting technology savvyconsumers to an entity (e.g., an insurance company) managing server 101.

FIG. 3 shows an automated damage assessment process 300 in accordancewith at least one aspect of the present disclosure. In certain aspects,an application related to damage assessment and claims processing may bedownloaded onto a mobile device (e.g., iPad™, iPhone™, Android™, etc.)associated with a user (e.g., a customer of an insurance company) tofacilitate one or more steps of the process in FIG. 3.

The process of FIG. 3 may start out at step 301 where a user (e.g., acustomer) associated with an entity managing enhanced claims processingserver 101 (e.g., insurance company) may enter a claim number (e.g., anumber related to damage associated with an insured vehicle, etc.) intoa damage assessment and claims processing application running on amobile device (e.g., network device 201). To generate a claim number, aclaimant may contact an entity managing enhanced claims processingserver 101 (e.g., an insurance company, etc.) with a first notice ofloss (FNOL). The claimant may contact the insurance company in anynumber of ways, including via agent, by phone, by email, via a companywebsite, etc. As part of the FNOL, the claimant may provide basicidentifying and/or validating information (e.g., name, age, claimnumber, etc.) and vehicle information, including the make, model, andyear of manufacture. The claimant may also provide the general areas ofdamage to the vehicle and any other relevant details (e.g., condition ofglass, under carriage, engine, wheels, airbags, etc. associated with thevehicle). In one embodiment, this information may be provided from aremote location (e.g., location of an accident, claimant's home, agent'soffice, etc.) using an application loaded onto a smart phone or tablet(e.g., iPad™, iPhone™, Android™, etc.).

The mobile device may then transmit the entered claim number and relatedinformation to enhanced claims processing server 101. The process maythen move to step 303 where server 101 may determine if the claim numberreceived in step 301 is valid. If server 101 determines that the claimnumber is not valid, then server 101 may transmit a message to themobile device, stating that the claim number is invalid in step 305. Theuser may then enter another claim number (step 301).

If server 101 determines that the claim number is valid, the process maymove to step 307 where server 101 may send the user instructions of thetypes of image data (e.g., photos, video, etc.) that should be capturedof damage associated with the insured vehicle. It should also be notedthat in some embodiments server 101 may not receive a claim number andmay proceed in providing user instructions on the types of image datathat should be captured without receiving a claim number. The user mayreceive instructions on various types of photos/video, includingphotos/video of the entire vehicle, VIN door tag, current odometerreading, and/or the damaged areas. In some aspects, the user may captureimage data related to at least two different angles of the damage foreach panel (e.g., hood, fender, door, bumper, etc.) based on an initialclaim description.

When the user of the mobile device receives these instructions, the usermay use a camera associated with the mobile device to take the photosand transmit these photos to the server 101. The user may be allowed topreview each photo before selecting the image. Once a photo has beenselected, the image may be shown on a display associated with the mobiledevice under a photo type (e.g., a photo of the entire vehicle, VIN doortag, current odometer reading, and/or damaged area). If the user is notsatisfied with any photo, the user may delete the photo by selecting itand then retake the photo. In some aspects, the user may annotate thephotos (e.g., by drawing a line from one end of the dent to the other,etc.) prior to transmitting them to server 101. In yet otherembodiments, server 101 may itself annotate any received photos/video.

In some embodiments, any approved photo may not be sent to server 101until all of the images have been captured. In some aspects, server 101may support a website interface through which photos may be uploaded bya user of a mobile device. Also, the use of multiple photos (e.g., viastereoscopic techniques), video (e.g., by walking around the vehicle togenerate a complete view), and/or three-dimensional photos/video mayassist in determining the depth of damage to a vehicle. In some aspects,determining the depth of damage may help in classifying the damage(e.g., a turbulent dent versus a dish dent). In addition, the degree ofdamage by area and depth may be automatically estimated through toolssimilar to ultrasound tools. Knowing the depth of damage may also assistin automatically determining the cost of repair or replacement. Inaddition, as the user is taking video/photos of damage associated withthe insured vehicle, a claims adjuster associated with an entitymanaging server 101 (e.g., an insurance company) may interface with theuser in real-time (e.g., via messaging, phone, email, etc.) as thephotos are being sent to the adjuster and/or as the video is beingstreamed to the adjuster and describe to the user the photos/video thatstill need to be taken and/or where to place a camera as thephotos/video are captured.

After server 101 receives image data transmitted from a mobile device instep 309, server 101 (or an individual/group associated with the entitymanaging server 101) may determine if the photos are acceptable in step311. For instance, server 101 may determine that the photos are tooblurry and/or that the photos do not capture the correct angles toclearly show damage associated with the insured vehicle. As an example,server 101 may employ a bar code scanning mechanism and/or an opticalcharacter recognition (OCR) system for detecting the VIN from asubmitted photo. In other aspects, the mobile device itself may use abar code scanning mechanism and/or an OCR system for determining the VINnumber. In this example, if the VIN cannot be detected from the photoand/or using these techniques, then the submitted photo may be deemed tobe unacceptable. If server 101 determines that that the photos are notacceptable, the process may move back to step 307 where the server 101may send the user instructions on what types of photos to take and/orwhat changes need to be made to the previously submitted photos. In yetother embodiments, a dispatcher associated with an entity managingserver 101 (e.g., an insurance company) may determine if submittedphotos are acceptable. In other embodiments, the mobile device mayitself determine if any given photo is blurry and/or inaccurate andprompt the user to retake the photo. In this aspect, the application fordamage assessment and claims processing running on the mobile device mayhave computer-executable instructions stored within a memory of themobile device for automatically detecting and/or rejecting a photo/videocaptured within a given category.

If server 101 determines that the photos are acceptable, server 101 mayattach the photos to the user's claim in a database associated withserver 101. Server 101 may also determine a damage estimate (e.g., anestimate for repairing and/or replacing any damaged parts) afteranalyzing the photos in step 313 based on predefined rules. The damageestimate may be generated by comparing the photos submitted by themobile device with photos of similarly damaged vehicles or with photosof non-damaged vehicles of similar make/model. To perform thiscomparison, server 101 may access a database (e.g., network device 201)of photos of vehicles with various types of damage and/or vehicles withno damage. To initially populate the database with photos for later use,each user may be required to upload various photos of a vehicle uponpurchase of the vehicle. Also, as server 101 analyzes recently submittedphotos, previously uploaded photos of a given vehicle may be used todetermine any pre-existing damage on the vehicle. Once database 201includes photos/video from many cases of vehicle damage, server 101 maydetermine a damage estimate for a new case based on the prior cases.

Server 101 may not need to build a new damage estimate piece-by-piecefor a given damaged vehicle. In this regard, server 101 (or anindividual/group associated with the entity managing server 101) maygenerate a new damage estimate based on a holistic view of a damagedvehicle. Over time, server 101 may build a database (e.g., networkdevice 201) of specific damage templates (e.g., damages to more than onepart of a vehicle that are commonly associated with one another) andestimated/actual costs for repairing damages associated with thesetemplates. Once this database has been built, damage estimatesassociated with subsequently analyzed vehicles may be generated from aholistic view of the vehicles by accessing information within thehistorical database.

For instance, if a first type of damage to the front bumper of a vehicleis commonly associated with a second type of damage to the headlights ofthe same vehicle and this damage template is associated with apredetermined repair cost in the database, server 101 may use thisrepair cost to generate a new estimate for subsequent vehicles thatexhibit damage similar to this damage template.

In one example, the damage estimates retrieved from the historicaldatabase may be adjusted based on differences associated with a currentcase. For instance, the damage estimate may be adjusted based on theaverage inflation rate (e.g., for parts, labor, etc.) between the dateat which the damage estimate within the historical database wasgenerated and the current date. In other embodiments, the damageestimate may be adjusted for small differences such as the make, model,and year of manufacture when the vehicle in the historical database andthe currently analyzed vehicle are compared. Similarly, the damageestimate may be adjusted based on differences in the precise damageassociated with the vehicle in the historical database and the damageassociated with the vehicle currently being analyzed. In yet otherexamples, the damage estimate may be adjusted based on the terms of aninsurance policy that covers damage to the insured vehicle currentlybeing analyzed. One of ordinary skill in the art would understand thatany number of factors may be considered when adjusting the damageestimate retrieved for vehicles stored in the historical database tomore accurately reflect a damage estimate for a currently analyzedvehicle.

In other aspects, when a vehicle exhibits more than one type of damage,server 101 may access the historical database multiple times (one foreach type of damage) and then add one or more interaction terms to thesum of the cost estimates for each type of damage. For instance,extending the example above of damage to a front bumper and to theheadlights of a vehicle, server 101 may generate a first damage estimatefor repairing the front bumper and a second damage estimate forrepairing the headlights. Server 101 may then add these two damageestimates to generate a total damage estimate.

In this embodiment, server 101 may also calculate an interaction term(which may be a positive or a negative value) that represents either anincreased (e.g., because the damages taken collectively introduce morecomplexity and are thus more expensive to repair than if handledindividually) or decreased (e.g., because the damages taken collectivelyhave overlapping repair procedures and are thus less expensive to repairthan if handled individually) cost of repairing the vehicle when both ofthese types of damages occur together. The effective total damageestimate may then be the sum of the total damage estimate and theinteraction term.

One of ordinary skill in the art would understand that a given damagetemplate may be built based on any number of specific damagetypes/locations. In addition, server 101 may generate any number ofinteraction terms for a given analysis. For instance, if a damageestimate is based on damage to three parts of a vehicle, server 101 maygenerate interaction terms that relate to increased/decreased costassociated with repair to the following part groups: the first twoparts, the first and third parts, the second and third parts, and allthree parts at once. In other embodiments, server 101 may generate aninteraction term for only some of the damaged parts.

In certain aspects, server 101 may also query the claimant with regardsto the type of third party service provider (e.g., repair shop, etc.)they would prefer after damage analysis and claims processing iscomplete.

In other aspects, exterior damage associated with the vehicle may beused to predict (e.g., via predictive modeling using the database ofpast assessed exterior/interior damage for other similar cases, etc.)the likelihood of interior (e.g., mechanical, cabin, etc.) damage to thevehicle and/or potential difficulties in repairing the vehicle.

Once the image data has been analyzed, server 101 may includecomputer-executable instructions to recognize the extent of damage tovarious parts of the vehicle (e.g., chassis, etc.), including varioustypes of dents and edge damage, and to identify various parts of thevehicle.

In some aspects, the detection of damage to the vehicle may be based onobject recognition algorithms that compare images (e.g., comparing x, y,and z coordinates of each point on the images) of the vehicle inquestion to reference images of similar vehicles (e.g., same model,make, year of manufacture, etc.) with no damage. More specifically,server 101 may access a database of images storing the reference imagesof vehicles of various models and makes. By using objectrecognition/edge detection algorithms (e.g., involving blur filters,gray-scaling, custom algorithms, etc.), server 101 may determine wheredamage is located as well as the potential size/area of the damage.Server 101 may also access internal/external databases storing images,damage depth map information (e.g., from previously assessed analyses,etc.), and/or processed claims reports from damaged vehicles that server101 has assessed previously. In particular, server 101 may accessimages/depth map information from previously assessed damaged vehiclesfor use as a guidepost in assessing the damage of a new vehicle. If noreference information (e.g., data, images) exists, axis symmetryinformation may also be used to identify possible irregularities and/ordamage.

In some aspects, the algorithm employed by server 101 may use acomparison of an image of a damaged vehicle with an image of anundamaged version of the same vehicle to “subtract out” and isolate thedamaged area of a vehicle. If an exact replica of an undamaged vehiclecorresponding to a damaged vehicle under study is not available for thiscomparison, server 101 may further use various additional imageprocessing algorithms, including blurring filters, etc. to detect adamaged portion of a vehicle.

In additional aspects, server 101 may grayscale all image data to makeprocessing faster. Further, edge filters may be applied to both theimage data from the damaged vehicle and its corresponding referenceimage data so that the edges of a damaged area may be “subtracted out”and identified in the image data of the damaged vehicle. Once thedamaged area has been identified in the image data, server 101 mayfurther process the damaged area to sharpen the area, to make the edgesmore prominent, and to fill any missing links found in the edges.Afterwards, server 101 may color, texture, and/or otherwise “fill in”the damaged area surrounded by the edges and extract the damaged areafrom the surrounding image data. Once the damaged area has beenisolated, server 101 may calculate the precise area of the damage.

Similarly, server 101 may determine the depth of a damaged area (e.g.,via stereoscopic methods, etc.) and may analyze raw depth data tofurther investigate points of interest (e.g., a point that has a muchlarger depth than surrounding points, etc.). Using this analysis, thedamaged area may be further characterized (e.g., a dented area may bedetected and if, for example, the general slope of the dent is high, thedent may be characterized as deep and rounded whereas if the slope islow, the dent may be characterized as shallow.)

In addition, if the server 101 retrieves image data or claims reportsassociated with a similar or the same previously analyzed vehicle thathas similar or the same types of damage (e.g., as a result of a similaraccident to a similar vehicle or part, etc.) as a vehicle currentlybeing analyzed, server 101 may use a damage analysis or cost estimate ofidentifying/repairing the damage or replacing a damaged part of thepreviously analyzed vehicle to generate a damage analysis/cost estimatefor the currently analyzed vehicle. In other words, server 101 mayperform one or more database queries to match characteristics of thecurrent analysis with previous analyses. For instance, the queries mayseek to match the size, depth, and location of a dent on a currentvehicle with a similar dent on a vehicle with a similar chassisconfiguration, make, model, and year of manufacture. For instance,consider a case where the vehicle in question is a new model that hasnot been analyzed before by server 101. In this scenario, server 101 mayattempt to match the vehicle currently being analyzed with its closestmatch, which in this case may be a similar model from the previous yearwith the same chassis configuration (e.g., a twin chassisconfiguration).

In matching a vehicle currently being analyzed with one that has beenpreviously analyzed, server 101 may assign a confidence factor to thematch. Server 101 may assign the highest confidence factor (e.g., aconfidence factor of 100%) to a comparison between the exact same typesof vehicles (e.g., cars of the same make, model, year of manufacture,etc.) having the exact same type of damage (e.g., a predetermined typeof dent, etc.). For instance, a comparison between vehicles with twocompletely different types of damage would have a confidence factor of0%. As the similarities between the currently analyzed vehicle andpreviously analyzed vehicles are reduced, server 101 may assign a lowerconfidence factor to the comparison. For instance, output drawn fromcomparisons between vehicles of the same make and model but withdifferent years of manufacture may be associated with a slightly lowerconfidence factor than 100%. In some aspects, confidence factors maydecrease further when vehicles of different models and years ofmanufacture (e.g., vehicles with different chassis configurations, trimline configurations, etc.) but the same make are compared. In oneembodiment, server 101 may assign a threshold confidence factor (e.g.,70%, etc.) below which output generated by a comparison performed byserver 101 may not be considered reliable. If the confidence factorassociated with a comparison between two vehicles falls below thisthreshold and there is no reliable comparison within the database,server 101 may then use physical details of the damage (e.g., size,location, area, etc.) to provide output such as a cost estimate fordamage repair/replacement and/or the amount of time required forrepair/replacement.

Server 101 may also use stored data to determine appropriate vendors forrepairing/replacing the vehicle and the amount of time forrepair/replacement. The wait time for repair/replacement may depend onvarious factors, including the size (e.g., area, depth, etc.),classification (e.g., turbulent dent, etc.), and location of the damage.

In addition, server 101 may determine if parts nearby to damaged partsmay also need to be blended into the damaged area. In other words, if apart of the vehicle needs to be refinished (e.g., repainted) eitherbecause it is being replaced or repaired, parts within a predetermineddistance of the repaired/replaced part may need to be blended (e.g.,color-matched) to the repaired/replaced part.

In some aspects, server 101 may acquire the knowledge of all previousclaims processed by server 101, as well as the knowledge of humanadjusters, to accurately process future claims. In this way, server 101may use machine learning to evolve its cost and/or repair estimationprocedure based on past experience.

To estimate the cost and repair/replacement time associated with thedamage to the vehicle and to determine whether to suggest that thevehicle be replaced or repaired, server 101 may also consider theextent/severity of the damage (area, depth, location, classification,etc.). For instance, damage to a character line (e.g., edge of a doorassociated with the vehicle) would be more difficult (e.g., moreexpensive and/or more time-consuming, etc.) to repair than damage to amore central location on the vehicle. Server 101 may also consider theactual cash value and the salvage value of the vehicle and any relevantlocal, state, and national laws in this analysis. In some aspects,server 101 may generate a rough cost estimate of repairing the damagejust based on the extent of the damage; then server 101 may refine thisestimate by analyzing previous cost estimates provided by server 101and/or actual repair data received from third party service providers(e.g., repair shops, etc.) that have repaired similar vehicles withsimilar damage. In additional aspects, server 101 may generate a basiccost estimate by taking into account factors such as the number of hourspredicted for the repair, the labor rate, and the current marketconditions. In this aspect, server 101 may compare this basic costestimate with the cost of merely replacing the vehicle (e.g., a totalloss) or the damaged part within the vehicle and based on thecomparison, server 101 may suggest the cheaper option. These estimatesmay also be transmitted to existing platforms (e.g., Audatex®,Mitchell®, etc.) for comparison purposes.

If the analyzed damage to the vehicle is different from the damageindicated by the claimant during the FNOL, server 101 may query theclaimant as to the discrepancy. For instance, if the claimant initiallyprovided information relating to damage on the left side of the vehiclebut server 101 discovers that the primary damage occurred on the rightside, server 101 may question the claimant as to when the damageoccurred (e.g., was the damage due to a previous incident or preexistingcondition?, is the claimant being truthful?, etc.). Server 101 may alsoask the claimant to sign a statement as to the truth of the informationprovided. The claimant may have the option of answering the questions asthey come up or the questions may be queued until the server 101 hasfinished processing the image analysis of the vehicle. If discrepanciesbetween the claimant's answers and the analyzed damage to the vehiclecontinue to exist, server 101 may request the involvement of a humanclaims adjuster.

In other embodiments, a technician associated with an entity managingserver 101 (e.g., an insurance company) may analyze the photos todetermine a damage estimate. Also, in certain aspects, the processdiscussed herein may allow a user to upload photos/video that fall intoalternative and/or additional categories (e.g., photos for each vehiclepart, etc.).

As part of the image/video damage analysis, server 101 may ask the userto compare damage associated with the insured vehicle to damage depictedin a series of photos/video sent by server 101. In other embodiments,server 101 may request that the user classify the type of damageassociated with the insured vehicle. For instance, server 101 may askthe user questions such as, “Does the damage to your vehicle look morelike the damage shown in photo A or photo B?” Server 101 may ask anynumber of questions until server 101 has reached a clear understandingof all the damage to the insured vehicle and a damage estimate can becalculated. In some ways, this process may allow the user to estimatethe damage to the insured vehicle.

As an example, consider a scenario where a driver's side door is dentedand the driver's side window is cracked in a four-door sedan. Assumethat the damage is centrally located on the driver's side window anddoor. Once server 101 receives a valid claim number related to thisdamaged sedan, server 101 may transmit, to a user device, one or moreimages depicting various types of damage to the driver's side window anddoor of four-door sedans that have been previously analyzed and/orstored in memory. The first image or images transmitted to the userdevice may be based on previously submitted information regarding anaccident that caused the damage or any other type of input provided by aclaimant and/or related parties. Thus, the first image or imagestransmitted to the user device may not depict damage that preciselyconforms to the damage of the sedan currently being analyzed. Forinstance, if two images are initially transmitted to the user device,one of the images may depict damage to the corner of the driver's sidewindow and door and the other image may depict damage that is locatedcloser to the center. In this scenario, a user of the user device (e.g.,a mobile phone), upon analyzing the two images, may select the imagethat depicts the centrally-located damage. The mobile device may thentransmit the selection to server 101, and server 101 may use thisinformation to generate a damage estimate.

Alternatively, suppose that both images initially transmitted fromserver 101 depict damage to the corner of the driver's side door andwindow in a four-door sedan. In this scenario, if both images areequally unrepresentative of the damage to the sedan in question, theuser may transmit a message to server 101, stating how the referenceimages are equally unrepresentative. In response to this message, server101 may transmit another image or images responsive to the informationprovided by the user in the message. Once again, the user may select oneor more images that most closely depict damage to the sedan in question.Suppose that, on the second pass, server 101 again transmits two imagesand that, in this instance, both images depict damage to four-doorsedans with centrally-located damage to the driver's side door andwindow. However, suppose that one of the images does not depict damagethat is as severe as that exhibited by the sedan in question. In thisscenario, the user may choose the image that depicts damage with theseverity level consistent with the damage to the sedan in question.

By iterating through multiple rounds of image analysis and data exchangebetween server 101 and a user device, server 101 may, with eachsuccessive round, determine more precisely the damage associated withthe sedan in question. When server 101 determines that the damage to thesedan has been fully characterized, server 101 may use the variousresponses provided by the user device to calculate a damage estimate forthe damage to the sedan and transmit a settlement based on thecalculated estimate.

In other embodiments, server 101 may transmit an insurance claim to aclaims adjuster for manual processing of the claim if server 101 cannotcalculate an accurate damage estimate after a predetermined number ofquestion/answer rounds.

In additional embodiments, the user may transmit audio (e.g., byspeaking into the mobile device, etc.) and/or an audio file thatincludes a description of what happened to cause the damage to thevehicle (e.g., the specifics of an accident, etc.). This audio/audiofile may be translated into text and incorporated into the photos/videoof damage and/or analyzed to determine if the damage matches anynarrative description provided by the user. Also, the user may transmita text file describing damage and/or an accident that caused the damage.In yet other embodiments, the user may capture and transmit the sound ofthe vehicle being started and/or the sound of the vehicle running toserver 101 (e.g., to determine if a muffler associated with the damagedvehicle is broken, etc.).

Based on the analysis and the damage estimate, server 101 may transmit aproposed settlement (e.g., cash compensation, etc.) for the assessedloss to the user of the mobile device in step 315. After the userreceives the proposed settlement, the user may notify server 101 whetheror not the proposed settlement is acceptable in step 317.

If the settlement terms are not acceptable, then the process may move tostep 319 where server 101 may transmit the settlement to a claimsadjuster for manual processing. If the settlement terms are acceptable,the process may move to step 321 where server 101 may transfer any fundsrelated to the assessed loss directly to a bank account associated withthe user.

In some aspects, users may provide feedback designed to evaluate theirexperience through process 300. This feedback may be used to improveprocess 300 for future users and may involve the use of surveys,questionnaires, email, etc.

In other aspects, server 101 may determine and/or transmit supplementaladjustments to an initial damage/repair estimate. For instance, server101 may determine that there is a 95% chance that repair option A mustbe performed, a 50% chance that additional repair option B must also beperformed, and a 10% chance that additional repair option C must also beperformed. When a repair shop examines the damage to a damaged vehicleand notices that there is less/additional damage, server 101 may usethis information to revise an initial damage estimate with asupplemental adjustment to the initial estimate. Also, in cases whereserver 101 predicts that there may be many supplemental adjustments(e.g., above a predetermined threshold number of supplementaladjustments) to the initial estimate of damage, a claims adjuster maymanually evaluate the damage and determine the likelihood of each of thesupplemental adjustments.

In addition, server 101 may provide the user with a list of repairfacilities for repairing the vehicle. Once the vehicle enters the repairprocess, messages may be pushed to the mobile device of the user toidentify where the vehicle is located is in the repair process (e.g.,which step of the repair process is the current step, etc.). Thesemessages may identify who is working on the vehicle and/or may includephotos/video of the vehicle as it is being repaired. The messages mayalso identify when the repair process may be completed.

In some aspects, some types of claims may be excluded from the automatedprocess illustrated in FIG. 3. These claims may include comprehensiveclaims, claims with injuries to any involved parties, claims involvingnon-drivable vehicles or air bag deployments, claims with lossdescriptions that include undercarriage/mechanical damage, claimsinvolving motorcycle and/or recreational vehicle (RV) losses, and claimsinvolving users that already have an estimate for damage associated withan insured vehicle.

FIGS. 4-8 show various display screens displayed to a user of a mobiledevice in accordance with at least one aspect of the present disclosure.FIG. 4 shows a series of initial display screens displayed when a userstarts a damage assessment and claims processing application stored on amobile device (e.g., network device 201) in accordance with at least oneaspect of the present disclosure. Screen 401 may be the initial screenthat the user views upon starting the application. Screen 401 may allowthe user to enter a claim number to begin a damage assessment and claimsprocessing method. In certain aspects, the claim number may be used tocompare a damage estimate generated by analysis of photos submitted bythe user to a damage estimate generated manually by a claims adjusterusing more conventional claims adjustment techniques. Once a user entersa valid claim number, the mobile device may display screen 403, wherethe user is presented with photo instructions that explain to the userthe types of photos that should be taken. Screen 403 may includeinstructions on taking photos of the entire insured vehicle, VIN doortag, current odometer reading, and any damaged areas of the insuredvehicle. When a user presses the “Get Started” button 403 a on screen403, the mobile device may display screen 405, which allows a user toselect and start taking any of the types of photos listed in screen 403(e.g., photos of the entire vehicle, VIN door tag, current odometerreading, and/or damaged areas). The “Submit Photos” button 405 a onscreen 405 may be inactive until at least one photo of each type istaken by the user.

FIG. 5a shows a first series of display screens displayed on a mobiledevice as a user takes photos of a damaged vehicle in accordance with atleast one aspect of the present disclosure. In display screen 501, theuser may select to take a photo of the entire vehicle, the VIN door tag,and/or the specific damaged area(s). In the example of FIG. 5a , a userselects to take a photo of the entire vehicle. When a user selects oneof the photo categories in screen 501, screen 503 may allow the user toselect the “Capture Photo” button 503 a to start the camerafunctionality within the mobile device, the “Adding Existing” button 503b to choose a photo from the photo roll, and/or the “Cancel” button 503c to cancel out of the previous command.

Assuming that the user selects the “Capture Photo” button 503 a inscreen 503, the mobile device may display screen 505 where instructionsrelated to the current photo type (e.g., a wide view of the entirevehicle) may be overlaid on top of the camera. The user may select the“OK” button 505 a on screen 505 to close the overlay and cause displayof the camera screen 507. Camera screen 507 may include a camera shutterbutton 507 a (e.g., for taking a photo) and flash button 507 b (e.g.,for turning the camera flash on/off). The “Instructions” button 507 c onscreen 507 may open the instructions overlay from screen 505, and the“Done” button 507 d on screen 507 may save all photos that have beentaken to a memory of the mobile device and may return the user to themain photos screen 501. When the user selects the shutter button 507 ain screen 507, the mobile device may display screen 509 to indicate thata photo is being taken. In some aspects, all buttons on screen 509 maybe disabled after the user selects the shutter button 507 a.

FIG. 5b shows a second series of display screens displayed on a mobiledevice as a user takes photos of a damaged vehicle in accordance with atleast one aspect of the present disclosure. Screen 511 may allow a userto preview a photo that has been taken and take an appropriate action onthis photo. In particular, the user may select a “Discard” button 511 ato discard the photo or a “Use” button 511 b to use the photo for damageassessment and claims processing. Assuming that the user selects “Use”button 511 b, the user may proceed to take other photos within theselected photo type. When the user has taken all the photos of a givenphoto type, the user may select the “Done” button 513 a on screen 513.After selecting the “Done” button 513 a on screen 513, the mobile devicemay display screen 515, where thumbnail image(s) of the photo(s) thatthe user has already taken may be displayed in the correspondingcategories.

FIG. 6 shows a series of display screens displayed on a mobile devicefor enabling a user to delete photos that have already been taken inaccordance with at least one aspect of the present disclosure. Screen601 displays thumbnails of all photos that have already been taken. Whena user selects one of the thumbnails in screen 601, the mobile devicemay display screen 603, where a series of buttons may be displayed,including an additional options button 603 a for displaying additionaloptions associated with the current photo (e.g., email photo, use photoas wallpaper, etc.), a scroll to previous photo button 603 b forscrolling to the previously-viewed photo in the photo reel, a play photoreel button 603 c for sequentially displaying each photo in the photoreel, a scroll to next photo button 603 d for scrolling to the nextphoto in the reel, and a delete button 603 e for deleting thecurrently-viewed photo. If the user selects delete button 603 e, thephoto currently displayed may be queued for deletion and mobile devicemay display screen 605. Screen 605 includes an action panel with a“Delete Photo” button 605 a for confirming that the currently-viewedphoto is to be deleted and a “Cancel” button 605 b for cancellingdeletion of the currently-viewed photo. If the user selects “DeletePhoto” button 605 a, the currently-viewed photo is deleted and the nextphoto in the current category is displayed in screen 607. If the userselects a back button 607 a on screen 607, the user may back out toreturn to photos screen 609. Screen 609 may display the remainingthumbnails stored in a memory of the mobile device, with the image thatthe user deleted in screen 605 removed from the list of thumbnails.

FIG. 7 shows a series of display screens displayed on a mobile devicefor enabling a user to submit photos for review by an enhanced claimsprocessing server 101, in accordance with at least one aspect of thepresent disclosure. Screen 701 may include a “Submit Photos” button 701a for submitting photos to server 101 when all photos have been taken.When a user presses “Submit Photos” button 701 a, the mobile device maydisplay screen 703, which includes an action panel with the “SubmitPhotos” button 703 a for confirming that the captured photos are to besubmitted to server 101 and a “Cancel” button 703 b for cancelling thesubmission. If the user selects “Submit Photos” button 703 a, the mobiledevice may display screen 705 where an upload progress bar may indicatethe progress of the photo upload. Once the photos have been fullyuploaded, the mobile device may display screen 707, which indicates thatthe photos have been uploaded and explains any next steps that should betaken.

FIG. 8 shows a series of display screens displayed on a mobile devicefor enabling a user to receive feedback from an enhanced claimsprocessing server 101 regarding previously submitted photos, inaccordance with at least one aspect of the present disclosure. Whenenhanced claims processing server 101 completes review of the photossubmitted in FIG. 7, server 101 may transmit a notification to themobile device that feedback is ready for review. When the mobile devicereceives the notification, screen 801, which includes a notificationthat feedback is ready, may be displayed. When a user selects the “ViewNotification” button 801 a, the mobile device may display screen 803,which may include a detailed description of any feedback received fromserver 101. In this case, server 101 has transmitted a message that asksthe user to take additional photos (e.g., of the damage to the left sideof a bumper). Screen 803 may also include a “Take Photos” button 803 awhich may allow the user to take additional photos of the damagedvehicle. When the user presses “Take Photos” button 803 a, the mobiledevice may display screen 805 which allows the user to take more photosof the damaged vehicle (e.g., in response to the feedback received inscreen 803) using the same process depicted in FIGS. 5a and 5 b.

Once all required photos have been taken, the user may press the “SubmitPhotos” button 807 a in screen 807 to submit the photos taken via screen805 to enhanced claims processing server 101. When the user presses the“Submit Photos” button 807 a in screen 807, the mobile device maydisplay screen 809, which includes a progress bar that shows theprogress of the photo upload to server 101.

Aspects of the disclosure allow for customers/potential customers of anentity managing enhanced claims processing server 101 (e.g., aninsurance company) to obtain advice about the advantages/disadvantagesof formally submitting an insurance claim for damage associated with aninsured item (e.g., a vehicle, home, etc.). In this regard, enhancedclaims processing server 101 may process information that addresses apre-claim consultation between potential customer/customer and an entitymanaging server 101. In particular, data analyzed by enhanced claimsprocessing server 101 may be used to assign a projected overall monetaryvaluation of a submitted claim for a given set of conditions associatedwith damage to an insured item so that a customer/potential customer maydecide whether or not to submit a claim.

In some aspects, a customer/potential customer of an entity managingenhanced claims processing server 101 (e.g., an insurance company) or anagent associated with the entity managing enhanced claims processingserver 101 may generate data (photos, video, descriptive text, etc.)associated with damage to an insured item. This data may be transmittedto enhanced claims processing server 101, where the data may be analyzedalong with data associated with the terms of an insurance policyassociated with (e.g., insuring) the damaged item.

In some aspects, an agent associated with the entity managing enhancedclaims processing server 101 may obtain details of an insurance policyassociated with a damaged item in one of several ways. For instance, ifthe damaged item is associated with a customer of the entity managingenhanced claims processing server 101, the agent may access a databaseassociated with enhanced claims processing server 101 for thisinformation. In other aspects, an agent of the entity managing enhancedclaims processing server 101 may simply ask a customer/potentialcustomer associated with the damaged item for details such as deducibleamounts, premium levels, special provisions, coverage limits, etc. ofthe relevant insurance policy. The agent may then transmit these detailsto enhanced claims processing server 101.

Enhanced claims processing server 101 may then analyze informationrelated to damage of the insured item and information related to anassociated insurance policy providing insurance coverage for the insureditem to determine consequences of formally submitting an insurance claimto seek compensation for the damage. For instance, by analyzing theextent of deductions associated with the insurance policy covering theinsured item and the extent that rewards (e.g., safe driver reward,etc.) will be lost for submitting a claim, enhanced claims processingserver 101 may calculate the extent that the premium amount associatedwith the insurance policy covering the damaged item will increase duringa subsequent term if the claim is submitted. In addition to calculatingan effect on premium and rewards, enhanced claims processing server 101may also calculate other effects such as a surcharge or probability ofrenewal. Based on this information, an agent associated with the entitymanaging enhanced claims processing server 101 may provide advice to thecustomer/potential customer on whether or not the customer/potentialcustomer stands to benefit by formally submitting the insurance claim.In other aspects, enhanced claims processing server 101 may directlytransmit this advice to a customer/potential customer.

In other aspects, this process may also allow enhanced claims processingserver 101 and/or an agent associated with the entity managing enhancedclaims processing server 101 to offer upsell materials. For instance, byexamining details of an accident, the type of insurance maintained bythe insured, and other details of the insured, including other assetsmaintained by the insured and other types of insurance maintained bypeople similar to the insured, enhanced claims processing server 101 mayprovide an offer for a new insurance product and/or discounts associatedwith already purchased insurance products to entice a customer/potentialcustomer to either become a customer of an entity managing enhancedclaims processing server 101 and/or to purchase additional productsoffered by the entity managing enhanced claims processing server 101.

FIG. 9 shows a flow chart 900 for providing pre-claim consultations inaccordance with at least one aspect of the present disclosure. Theprocess may begin at step 901 where enhanced claims processing server101 may receive data related to damage of an insured item. Server 101may receive this data, for example, through a mobile device operated bya user and/or through an agent associated with an entity managing server101.

Once this data is received, server 101 may determine if the insured itemis associated with a current customer of the entity managing server 101in step 903. If the insured item is not associated with a currentcustomer of an entity managing server 101, server 101 may receivedetails of an insurance policy insuring the insured item directly fromthe potential customer (e.g., via a mobile device, etc.) and/or from anagent associated with the entity managing server 101 in step 905. If theinsured item is associated with a current customer of an entity managingserver 101, server 101 may access information related to details of aninsurance policy associated with the insured item from an associateddatabase (e.g., a database of customer information) in step 907.

Either from step 905 or 907, the process may move to step 909 whereenhanced claims processing server 101 may analyze data related to damageof the insured item and information related to the relevant insurancepolicy. Based on this analysis, server 101 may calculate the overallconsequences (e.g., overall monetary valuation of benefit/detriment) ofsubmitting an insurance claim for damage to the insured item in step911. For instance, server 101 may calculate the overall monetaryvaluation by examining a projected increase in premium amount and aprojected refund (e.g., settlement amount) for submitting the claim.Once the overall consequences are calculated, the process may then moveto step 913 where server 101 may transmit the calculations to apotential customer/customer. Server 101 may also offer a suggestion orother information to help the potential customer/customer decide whetheror not to submit an insurance claim for the damaged item.

The process may also move optionally to step 915 where server 101 maytransmit upsell materials (e.g., information about newproducts/services, special promotions, etc.) based on customer details,insurance policy details, damage details, etc.

As an example, consider a scenario where a customer of an insurancecompany gets into an at-fault automobile accident that damages the frontfender of his car. Assume that the customer drives the car to a branchoffice of the insurance company where he has an automobile insurancepolicy. The customer seeks advice on whether or not he should submit aclaim for damage to his car. The insurance agent at the branch officemay take several photos of the damaged fender and may transmit thisinformation to enhanced claims processing server 101, along with detailsassociated with the customer (e.g., name, age, insurance policy number,etc.).

Once this information is received, server 101 may first determine if thereceived photos clearly depict damage to the insured vehicle. If they donot clearly depict any damage, server 101 may request additional photosfrom the customer and/or from the insurance agent. Once all relevantphotos have been taken, server 101 may access the relevant insurancepolicy covering the damaged vehicle.

Assume that in this scenario, the customer pays a $100 monthly premiumwith a zero deductible to maintain his insurance policy. Also, assumethat enhanced claims processing server 101 calculates that the ratingplan for his insurance policy dictates a premium increase of $50 a monthfor a one-year period (accident-free) for the severity of accident thathe experienced. Finally, assume that enhanced claims processing server101 further estimates that the assessed damage to his automobile is$500. Thus, server 101 calculates that he would pay an extra $600 ($50times 12 months=$600) in premium during the course of the subsequentyear and a settlement amount of $500 for assessed damage, if he were tosubmit the claim.

In this scenario, server 101 may transmit a summary of the monetaryvaluation and suggest that the customer could choose not to submit theclaim, given that the overall increase in premium exceeds the benefit(i.e., settlement amount) from submitting the claim.

Further aspects of the disclosure allow for customers of a given entitymanaging enhanced claims processing server 101 (e.g., an insurancecompany) to obtain insurance claim advice from a third party entityprior to submission of a claim for damage to an insured item. The thirdparty entity may be another insurance company, an insurance broker, orsome other entity separate from the entity at which the insured is acustomer. An enhanced claims processing server 101 associated with athird party entity may obtain details (premium amounts, deductibleamounts, coverage limits, etc.) about an insurance policy associatedwith an insured item and information about damage associated with theinsured item from the insured, from the entity at which the insured is acustomer, and/or from a public source (e.g., public records databasesthat store accident information, etc.). In one embodiment, this aspectof the disclosure may allow consumers to obtain insurance adviceanonymously (e.g., by entering relevant information related to damage ofan insured item through a website).

In some aspects, enhanced claims processing server 101 associated with athird party entity may infer details about an insurance policyassociated with the insured based on known details about insurancepolicies maintained by other consumers with characteristics similar tothe insured. For instance, if the third party entity is anotherinsurance company, the third party entity may itself maintain a customerdatabase that stores customer information like age, occupation, incomelevel, etc. and information about insurance policies maintained by thesecustomers. In this scenario, server 101 associated with the third partyentity may match characteristics of the insured to characteristics ofcurrent customers of the third party entity. Once matched, server 101associated with a third party entity may infer that characteristics ofinsurance policies maintained by customers similar to the insured arealso associated with an insurance policy maintained by the insured.

If the third party entity is not an insurance company and/or if thethird party entity does not have access to customer information storinginsurance policy details, enhanced claims processing server 101associated with a third party entity may use other methods to inferinsurance policy details associated with the insured. For instance,server 101 associated with a third party entity may run algorithms thatapproximate insurance policy details associated with a given consumerbased on inputs such as age, gender, income level, the insured itemunder consideration, etc.

Once enhanced claims processing server 101 associated with a third partyentity has calculated details about an insurance policy that insures adamaged item that is associated with a consumer that is not currently acustomer of the third party entity, server 101 associated with a thirdparty entity may analyze the information related to the damageassociated with an insured item and other information related to theinsurance policy that insures the damaged item to calculate an overallmonetary valuation of submitting an insurance claim for damage to theinsured item.

Based on the overall monetary valuation, enhanced claims processingserver 101 associated with a third party entity may suggest whether ornot to submit an insurance claim for damage to the insured item. Asbefore, the monetary valuation may consider information such as aprojected amount by which a premium of an insurance policy maintained bythe insured will increase and a projected settlement amount that will bepaid to the insured for damage associated with assessed loss to theinsured item, among other things.

In other aspects, enhanced claims processing server 101 associated witha third party entity may provide other incentives/services to a consumerwhen the consumer seeks advice prior to formal submission of aninsurance claim for damage associated with an insured item. Forinstance, after transmitting, to the consumer, a suggestion of whetheror not to submit an insurance claim for damage to an insured item,server 101 associated with a third party entity may offer to pay for theassessed loss (or a portion thereof) associated with damage to theinsured item, if the consumer will agree to become a customer of thethird party entity. In this regard, enhanced claims processing server101 associated with a third party entity may offer a customizedinsurance product that may better cover damage to the insured itemand/or that may result in a better overall monetary valuation offormally submitting a claim for damage to the insured item.

FIG. 10 shows a flow chart 1000 for providing pre-claim consultationswith a third party entity in accordance with at least one aspect of thepresent disclosure. The process may start out at step 1001 where anenhanced claims processing server 101 associated with a third partyentity may receive data related to damage of an insured item. Server 101may receive this data in a variety of ways, such as via a mobile deviceof a consumer associated with the damaged item, via an agent associatedwith the third party entity, etc. The process may then move to step 1003where server 101 associated with the third party entity may evaluateinformation related to an insurance policy associated with the insureditem. As outlined above, server 101 may evaluate this information in avariety of ways. Because the insured is not a customer of the thirdparty entity, server 101 associated with the third party entity maydetermine information related to an insurance policy associated with theinsured item directly from the insured, by evaluating known insurancepolicy details of people similar to the insured, by running an algorithmthat uses publicly available information related to insurance purchasingtendencies of those with predetermined characteristics, etc.

The process may then move to step 1005 where server 101 associated witha third party entity may analyze the data related to damage of theinsured item and the information related to an insurance policy of theinsured. Based on this analysis, enhanced claims processing server 101associated with a third party entity may calculate an overall valuationof submitting an insurance claim for damage associated with the insureditem in step 1007. This valuation may consider information such as aprojected premium increase for maintaining an insurance policyassociated with the damaged item and a projected settlement amount forassessed damage associated with the insured item, if a claim for thedamage is actually submitted.

Next the process may move to step 1009 where enhanced claims processingserver 101 may transmit, to either an agent associated with a thirdparty entity and/or the consumer in question, a suggestion or otherinformation to help the consumer decide whether or not to submit aninsurance claim for damage associated with the insured item. Finally, instep 1011, enhanced claims processing server 101 may transmit, to eitheran agent associated with a third party entity and/or the consumer inquestion, one or more incentives based on consumer details (age, gender,etc.), insurance policy details (level of coverage, premium levels,deductible amounts, etc.), and/or details associated with a damageditem. These incentives may relate to an offer for insurance that bettercovers the assessed loss for damage to the insured item and/or an offerto pay for the assessed loss (or a portion thereof), if the insuredagrees to become a customer of the third party entity. Also, if theinsured agrees to purchase an insurance policy offered by the thirdparty entity, these incentives may also relate to an extension ofaccident forgiveness for an accident related to the pre-claimconsultation in question.

As an example, consider a scenario where a consumer goes to an insurancecompany for a second opinion on damage associated with her insuredvehicle. Assume also that she is dissatisfied with the advice given toher by the insurance company at which she is a customer, and so shearrives at a third party insurance company to determine if other optionsmight be available to her.

An insurance agent associated with the third party entity may obtaindemographic details associated with the consumer and may transmit thesedetails to an enhanced claims processing server 101 associated with thethird party insurance company. These details may include informationrelated to age, income level, and address of the consumer in question,among other things. The insurance agent associated with the third partyentity may also help the consumer take a few photos of her damagedvehicle and may transmit these images to server 101 associated with thethird party entity.

In this particular scenario, assume that the consumer is reluctant todivulge the details of her insurance policy with the third partinsurance agency. Therefore, server 101 associated with the third partyinsurance company may cross-reference her demographic characteristicswith those of people similar to her that are already customers of thethird party insurance company. Server 101 associated with the thirdparty entity may then evaluate characteristics of insurance policiesmaintained by people similar to the consumer in question and may inferthat these characteristics are also characteristics of an insurancepolicy maintained by the consumer in question.

Server 101 associated with the third party entity may then analyze theimage data depicting damage to her damaged vehicle to assess the lossassociated with the damage. This analysis, combined with inferreddetails about the insurance policy maintained by the consumer, may beused to estimate an overall monetary valuation of submitting aninsurance claim for damage associated with her vehicle. Assume that inthis case, the consumer in question pays a $50 monthly premium tomaintain her automobile insurance policy and has a $500 deductibleassociated with this policy. Assume also that enhanced claims processingserver 101 associated with the third party entity determines that theassessed loss associated with her vehicle is $300 and that her monthlypremium will increase by $20 per month for a six month period (afterwhich it will return to $50 per month) if she were to submit a claim forher loss. Thus, server 101 associated with the third party entity mayestimate that the consumer in question stands to benefit very little bysubmitting a claim for her loss (as the assessed loss is less than herdeductible and her premium would increase as a result of the submittedclaim). Therefore, enhanced claims processing server 101 associated withthe third party entity may suggest that she could choose not to submit aclaim for this loss.

In this scenario, enhanced claims processing server 101 associated withthe third party entity may further suggest additional insurance productsto the consumer. These insurance products may be tailored to bettercover the type of damage associated with her vehicle. For example,enhanced claims processing server 101 associated with the third partyentity may suggest an insurance product that has a lower deductible(e.g., a $100 deductible) with a smaller increase in premium foraccidents of the nature experienced by the consumer. To furtherincentivize this insurance product, enhanced claims processing server101 associated with the third party insurance company may offer to payfor the assessed loss (i.e., $300) if the consumer in question agrees tobecome a customer of the third party insurance company.

In both the processes discussed in FIG. 9 and FIG. 10, an agent of anentity managing enhanced claims processing server 101 may perform amanual calculation to estimate any effects of formally submitting aninsurance claim for loss associated with an insured item.

Aspects of the disclosure enable a user device (e.g., mobile phone,tablet, etc.) to serve as a portal for efficiently providing access toservices provided by third party entities to consumers (e.g., customers,potential customers) who are undergoing a claims adjustment process as aresult of damage to an insured item. In this aspect, a consumer and/oran agent associated with an entity (e.g., an insurance company) managingenhanced claims processing server 101 may transmit, to server 101,images, video, and/or data related to damage associated with an insureditem, and server 101 may stream this information to a third party entity(e.g., a preferred partner of the entity managing server 101) inreal-time as server 101 is analyzing this information to assess damageassociated with the insured item.

A third party entity may provide any of various types of services thatmay be of interest to a consumer. For instance, a third party entity mayrepresent a repair agency for repairing damage to damaged vehicles. Byviewing the damage to a damaged vehicle as the claims adjustment processis still on-going, the repair agency may be able to estimate anapproximate cost and best strategy for repairing the damage, therebyallowing an entity managing enhanced claims processing server 101 andassociated consumers to plan the repair process much more efficiently.Enhanced claims processing server 101 may also transmit informationrelated to damage of an insured item to multiple repair agencies, forexample, to compare repair cost estimates and repair strategies.

Moreover, server 101 may use feedback received from third party entitiessuch as repair agencies in the claims adjustment process itself (e.g.,for generating a settlement value for settling claims related to thedamage). For instance, enhanced claims processing server 101 maygenerate (e.g., by analyzing data related to damage of an insured itemand other information related to an insurance policy maintained by aconsumer associated with the insured item) a first cost estimate forrepairing damage associated with an insured item and may receive asecond cost estimate for this repair from a third party repair shop. Ifthe first cost estimate and the second cost estimate differ by apredetermined threshold, server 101 may then compare the two values tocalculate a final cost estimate for repairing the damage to the insureditem and thereby settling an insurance claim related to the damage.

Third party entities may also represent other entities such asjunkyards, vehicle dealers, governmental agencies, etc. For instance,consumers may be interested in allowing junkyards to view damageassociated with an insured car to estimate how much compensation theywould receive for the car if the car was declared a total loss.Similarly, a consumer may be interested in allowing vehicle dealers toview damaged vehicles to estimate trade-in values if the consumer wereinterested in trading in a damaged vehicle for another vehicle.Moreover, consumers may be interested in transmitting informationrelated to damage of an insured item to governmental agencies such aspolice stations to allow these agencies to process items such asaccident reports, etc. related to the damage.

Using this process, rather than taking pictures with a phone and thensubmitting the pictures to a third party entity such as a repair agency,the repair agency may obtain damage information in real-time while anagent or consumer associated with an entity managing enhanced claimsprocessing server 101 is holding the phone and gathering image data fromdifferent angles around the damaged item. In other aspects, third partyentities such as repair agencies may analyze streamed data, images, andvideo as it is being sent and save only those portions that are ofinterest (e.g., those portions that clearly depict damage to the insureditem). In yet other aspects, customers/potential customers/agentsassociated with an entity managing enhanced claims processing server 101may transmit audio information (e.g., a description that explains videoand images being streamed) related to damage associated with an insureditem in real-time to third party entities.

In additional aspects, a third party entity receiving informationrelated to damage of an insured item may, upon viewing the information,request additional information and/or images. Enhanced claims processingserver 101 may transmit the request to a user device and may receive therequested information from the user device for transmission to the thirdparty entity.

FIG. 11 shows a flow chart 1100 for using a user device to allow a thirdparty entity to learn about damage to an insured item while the damageis still being assessed through a claims adjustment process inaccordance with at least one aspect of the present disclosure. Theprocess may start out at step 1101 where enhanced claims processingserver 101 may receive data related to damage of an insured item. Oncethe data is received, server 101 may immediately (e.g., in real-time)forward the data to a third party entity in step 1103. The third partyentity may analyze the data and, if additional data is required, maytransmit a request for this additional data in step 1105.

Enhanced claims processing server 101 may transmit this request foradditional data to a user device in step 1107 and may receive a responsewith the additional data in step 1109. Finally, in step 1111, server 101may forward this additional data to the third party entity.

As an example, consider a scenario where a customer of an insurancecompany drives his car to a local branch office so that the agent at thebranch office can assist him in filing a claim for an accident whichcaused damage to the front windshield of his car.

The insurance agent at the branch office may use his tablet computer totake images of the damaged windshield and may transmit this informationto enhanced claims processing server 101. As the insurance agent istaking photos of the damaged windshield, enhanced claims processingserver 101 forwards the image data in real-time to a preferred repairshop.

The repair shop analyzes the information as it is being sent andgenerates a cost estimate for repairing the broken windshield. Therepair shop then transmits this cost estimate to enhanced claimsprocessing server 101 so that the insurance agent and the customer canuse this information in assessing the damage and deciding on a vendorfor repairing the broken windshield.

In additional aspects of the disclosure, an agent associated with anentity managing enhanced claims processing server 101 (e.g., aninsurance company) may use a user device (e.g., mobile device, tablet,etc.) to capture damage data (e.g., images, video, text, etc.)associated with damage to an insured item so that a customer/potentialcustomer of the entity managing enhanced claims processing server 101may review the data for completeness and accuracy. This particularaspect of the disclosure may reduce the number of potential errors andlikelihood of fraud associated with capturing images related to damageof an insured item (e.g., because an agent associated with the entitymanaging enhanced claims processing server 101 is capturing imagesrather than the customer/potential customer of the entity managingenhanced claims processing server 101). In addition, a potentialcustomer/customer of an entity managing enhanced claims processingserver 101 may not have to wait at the entity managing enhanced claimsprocessing server 101 (e.g., an insurance company) for a claims adjusterto review and analyze damage data, because an agent may submit captureddamage data to enhanced claims processing server 101 once appropriateimages have been captured. Furthermore, as some potentialcustomers/customers of an entity managing enhanced claims processingserver 101 may not possess a user device (e.g., mobile device, tablet,etc.) configured to capture damage data, this aspect of the inventionfacilitates access of services to these customers/potential customers,as an agent associated with the entity managing enhanced claimsprocessing server 101 may use his or her own user device to capturedamage data.

In general, damage data may depict damage using various technologies(e.g., 3-dimensional images for depth information, panoramic images,video data, etc.) to allow different types of information to be gleaned.In addition to video and image data generated by an agent and/or acustomer/potential customer associated with an entity managing enhancedclaims processing server 101, agents and customers/potential customersmay also transmit a verbal description of damage to enhanced claimsprocessing server 101.

If a customer/potential customer of an entity managing enhanced claimsprocessing server 101 finds no problems with the damage data, the datamay be forwarded to enhanced claims processing server 101 (e.g., via anagent, directly from a customer/potential customer of an entity managingenhanced claims processing server 101, etc.). If a customer/potentialcustomer of an entity managing enhanced claims processing server 101determines that there are problems, the customer/potential customer maytransmit these concerns to the agent so that the agent can address themprior to transmitting the damage data to enhanced claims processingserver 101. In some aspects, a customer/potential customer of an entitymanaging enhanced claims processing server 101 may certify that damagedata shows only damage from a most recent accident (and excludes priordamage).

In some aspects, a customer/potential customer of an entity managingenhanced claims processing server 101 may receive an Internet link(e.g., as part of a message) to damage data captured by an agentassociated with the entity managing enhanced claims processing server101. A customer/potential customer of an entity managing enhanced claimsprocessing server 101 may then review the received damage data and, ifrequired, may add information to the received data set and/or modify thereceived data set before transmitting the received data and anyadditional/modified data back to a user device associated with theagent. In yet other aspects, an agent associated with an entity managingenhanced claims processing server 101 may request additional damage datafrom a potential customer/customer and upon receipt of this request, apotential customer/customer may capture the requested data prior totransmitting the data for review by the agent.

A customer/potential customer of an entity managing enhanced claimsprocessing server 101 may also receive other types information from auser device associated with an agent of an entity managing enhancedclaims processing server 101. For instance, if an entity managingenhanced claims processing server 101 is an insurance company, an agentassociated with the insurance company may use a user device to transmitinformation about insurance products, discounts, and/or rewards offeredby the insurance company. A customer/potential customer of the insurancecompany may review this information and transmit to the agent anindication of whether or not he wants to take further action (e.g.,purchase, request more information, etc.) on products presented to thecustomer/potential customer.

FIG. 12 shows a login screen displayed on a user device (e.g., mobilephone, tablet, etc.) in accordance with at least one aspect of thepresent disclosure. Login screen 1201 may allow an agent associated withan entity managing enhanced claims processing server 101 to enter ausername and password to login to an application and access capabilitiesrelated to capturing damage data associated with an insured itemowned/operated by a potential customer/customer of an entity managingenhanced claims processing server 101.

FIG. 13 shows two display screens displayed on a user device that allowa user to capture damage information associated with a new claim and/oraccess information related to claims that have been previously submittedfor claims adjustment, in accordance with at least one aspect of thepresent disclosure. In some aspects, screens 1301 and 1303 and futuredisplay screens discussed herein may be displayed only after a userenters login information (e.g., through screen 1201). If an entitymanaging enhanced claims processing server 101 is an insurance company,an insurance agent associated with the insurance company may accessscreen 1301 to create a new claim (e.g., for a damaged vehicle) forclaims adjustment by selecting the “Get Started” button in section 1301a, view a summary of claims that have been initiated by the insuranceagent and that are currently being analyzed by a claims adjuster (e.g.,“active estimates”) by selecting section 1301 b, and view a summary ofclaims that have been initiated by the insurance agent and that havealready been analyzed by a claims adjuster (e.g., “complete estimates”)by selecting section 1301 c.

Meanwhile, screen 1303 shows an alternative arrangement of informationfor allowing an insurance agent to create new claims for claimsadjustment and/or view claims that have already been submitted. Byselecting the “Get Started” button in section 1303 a, an insurance agentmay be directed to other screens that will allow him to capture damageinformation related to a new claim. In addition, section 1303 b shows asummary of active claims initiated by the insurance agent in question.Section 1303 b includes information such as a customer name to which agiven claim corresponds, an insurance policy number associated with theclaim, a claim number, the name of the insurance agent associated withthe claim, the name of a claims adjuster processing the claim, contactinformation for the claims adjuster, the status of the claim, and thetime/date of the last status update, along with a link to any newmessages received in connection with the processing of a given claim.Screen 1303 may also include section 1303 c, which includes a summary ofall claims initiated by the insurance agent in question and that havecompleted the claims adjustment process.

FIG. 14 shows two display screens displayed on a user device fordisplaying messages associated with a given claim, in accordance with atleast one aspect of the present disclosure. Screen 1401 shows a messagehistory in section 1401 a between two people associated with a givenclaim (e.g., an insurance agent who initiated the claim and a claimsadjuster reviewing claim information, etc.). New messages may be enteredby using the keypad shown in section 1401 c and by selecting the “Send”button 1401 b.

Screen 1403 shows a second display screen with a message history 1403 abetween people involved with a claim. The message history 1403 a shownin screen 1403 also includes enhanced features such as a “Retake VINPhoto” button 1403 b that may allow one of the participants of theconversation to retake a photo associated with a vehicle identificationnumber (VIN) of a vehicle that is being processed in related to theclaim. In addition, screen 1403 also includes a “Send” button 1403 c toallow one of the participants of the conversation to send a new message.

FIG. 15 shows a first set of two display screens displayed on a userdevice for providing user instructions for capturing images related todamage associated with an insured item, in accordance with at least oneaspect of the present disclosure. Screen 1501 includes a window 1501 aand instructions 1501 b for capturing a predetermined type of image ofthe damage associated with an insured item. For instance, in thisparticular example, window 1501 a and instruction 1501 b both relate tocapturing a close-up image of damage associated with an insured vehicle.After reviewing the image in window 1501 a and the related hintspecified by instruction 1501 b, an insurance agent associated with anentity managing enhanced claims processing server 101 may capture anappropriate type of image with a user device by selecting the “TakePhotos” button 1501 c. In addition, an insurance agent may requestfurther instructions on how to capture relevant images by selecting the“Next Hint” button 1501 d.

Meanwhile, screen 1503 includes a second window 1503 a and associatedinstruction 1503 b for capturing a second type of image associated withdamage to an insured item. For instance, window 1503 a and instruction1503 b relate to capturing damage to an insured vehicle from differentangles. If a user (e.g., an insurance agent) is ready to capture, with auser device, the type of images specified by window 1503 a and hint 1503b, the user may select the “Take Photos” button 1503 c. Alternatively,if the user needs further instructions on capturing relevant images, theuser may select the “Next Hint” button 1503 d. It should be noted thatthe type of images specified by screen 1501 and 1503 are exemplary, andany number of other types of images may also be requested.

FIG. 16 shows two display screens that display images of damage beingcaptured by a user device, in accordance with at least one aspect of thepresent disclosure. Screen 1601 includes a viewfinder window 1601 awhere a given type of image specified by instruction 1601 b (e.g., aclose-up view of a damaged area) is put into focus with an imagingdevice (camera, etc.) associated with a user device on which anapplication supporting this functionality is running. Once a user isready to capture the image seen in viewfinder window 1601 a, the usermay capture the photo by selecting the “Take Photo” button 1601 c.

Meanwhile, screen 1603 includes a different viewfinder window 1603 awhere a different type of image specified by instruction 1603 b (e.g., aview of a damaged area from a different angle) is put into focus with animaging device (e.g., camera) associated with a user device. Again, oncea user is ready to capture the image seen in viewfinder window 1603 a,the user may capture the image by selecting the “Retake Photo” button1603 c (assuming a first version of the photo has already been taken).

FIG. 17 shows a second set of two display screens displayed on a userdevice for providing user instructions for capturing images related todamage associated with an insured item, in accordance with at least oneaspect of the present disclosure. Screen 1701 includes a window 1701 aand associated instruction 1701 b for capturing a given type of image.In this particular example, window 1701 a and instruction 1701 b directa user to capture images of each corner of an insured vehicle. If a useris ready to capture the images, the user may select the “Take Photos”button 1701 c. Alternatively, if a user needs further instructions oncapturing relevant images, the user may select the “Next Hint” button1701 d.

Screen 1703 includes a window 1703 a and associated instruction 1703 bfor capturing a different type of image. In this example, window 1703 aand instruction 1703 b direct a user to take images of an entirevehicle. As before, if a user is ready to capture the images, the usermay select the “Take Photos” button 1703 c. Alternatively, if a userneeds further instructions on capturing relevant images, the user mayselect the “Next Hint” button 1703 d.

FIG. 18 shows a display screen with visual aids for aiding a user inproperly positioning an imaging device associated with a user device tocapture images related to damage of an insured item, in accordance withat least one aspect of the present disclosure. Screen 1801 may include awindow 1801 a with visual aids 1801 b to aid a user in positioning animaging device (e.g., a camera) associated with a user device (e.g.,tablet, mobile phone, etc.) so that the imaging device correctlycaptures an image associated with instruction 1801 c. In this particularexample, window 1801 a includes markers for positioning a camera so thatthe front and driver's side of a damaged vehicle appear in the properlocation of an image. Once a camera is properly positioned, a user(e.g., an insurance agent associated with an entity managing enhancedclaims processing server 101) may select the “Retake Photo” button 1801d (assuming a first but somehow defective version of this image hadalready been taken).

FIG. 19 shows two display screens displayed on a user device fordisplaying instructions related to capturing images for processing aclaim associated with damage of an insured item, in accordance with atleast one aspect of the present disclosure. In this particular example,screens 1901 and 1903 include images associated with a vehicleidentification number (VIN) and odometer reading associated with adamaged vehicle. Screen 1901 includes a viewfinder window 1901 adisplaying an image of a VIN tag associated with a damaged vehicle.Screen 1901 also includes an instruction 1901 b for capturing the VINtag displayed in window 1901 a. If a user (e.g., an insurance agent) isready to capture an image displayed in viewfinder window 1901 a, theuser may select the “Retake Photo” button 1901 c (assuming a first butsomehow defective version of this image had already been taken). Inalternative embodiments, a user may enter in a VIN through a keypad on auser device and/or may scan the VIN optically (e.g., as a barcode).

Meanwhile, screen 1903 includes a viewfinder window 1903 a displaying anodometer reading associated with a damaged vehicle. Screen 1903 alsoincludes an instruction 1903 b for capturing the odometer readingdisplayed in window 1903 a. If a user (e.g., an insurance agent) isready to capture an image displayed in viewfinder window 1903 a, theuser may select the “Retake Photo” button 1903 d (assuming a first butsomehow defective version of this image had already been taken).Alternatively, if a user is satisfied with the image already capturedfor this step, the user may move to the next step by selecting the “NextStep” button 1903 c.

FIG. 20 shows two display screens displayed on a user device forreviewing images depicting damage to an insured item, as captured by animaging device, in accordance with at least one aspect of the presentdisclosure. Screen 2001 includes an image 2001 a and instructions 2001 brelated to user review of captured images. Once a user (e.g., aninsurance agent associated with an entity managing enhanced claimsprocessing server 101, a potential customer/customer of an entitymanaging enhanced claims processing server 101) has reviewed andunderstood instructions 2001 b, the user may select the “Continue”button 2001 c.

Meanwhile, screen 2003 includes an image 2003 a that depicts an insureditem (e.g., a vehicle) and that has already been captured by an imagingdevice associated with a user device (e.g., a mobile phone, tablet,etc.). Screen 2003 also includes various options related to image 2003a; for instance, screen 2003 includes a “Remove” button 2003 b fordeleting image 2003 a from a memory associated with the user device onwhich image 2003 a is stored, a “Retake” button 2003 c for recapturingimage 2003 a, and an “Add Photo” button 2003 d for adding another photorelated to damage associated with an insured item.

FIG. 21 shows a display screen displayed on a user device for displayingclaim information associated with damage to an insured item, inaccordance with at least one aspect of the present disclosure. Screen2101 includes a section 2101 a for entering contact informationassociated with a claim, such as a customer name 2101 b and a submittername 2101 c (e.g., an insurance agent associated with an entity managingenhanced claims processing server 101). Screen 2101 also includes asection 2101 d for entering claim information such as a claim number2101 e associated with damage to an insured item and a section 2101 ffor entering policy information such as a policy number 2101 gassociated with an insurance policy covering damage to the insured item.Finally, screen 2101 may also include a section 2101 h for addingadditional details associated with the claim in question. Theseadditional details may relate to special processing instructions,information on any of the images captured in relation the claim, etc.Once all information has been entered, a user may select the “Submit forEstimate” button 2101 i for submitting the claim for review by a claimsadjuster.

FIG. 22 shows an automated damage assessment process 2200 in accordancewith at least one aspect of the present disclosure. In certain aspects,a mobile device (e.g., iPad™, iPhone™, Android™, etc.) associated with auser (e.g., a customer of an insurance company) may interact with aserver, such as server 100, to facilitate one or more steps of theprocess in FIG. 22. For example, a mobile device that implements theprocess of FIG. 22 may interact with a server that implements theprocess of FIG. 3.

The process of FIG. 22 may start out at step 2201 where a user (e.g., acustomer) associated with an entity managing enhanced claims processingserver 101 (e.g., insurance company) may receive, at a mobile device(e.g. network device 201), an application associated with the entity(e.g., by downloading the application from an application store). Theapplication may be configured to allow the user to submit informationabout an insurance claim event (e.g., a vehicle accident) to server 101.

The process may then move to step 2203 where the mobile device mayexecute the received application. The application may be configured withthe user's information, such as a customer identification number (e.g.,policy number) for the user within the entity's customer database (e.g.,database 203).

The process may then move to step 2205 where the mobile device transmitsa request to process a claim to server 101. For instance, the user mayenter a claim number (e.g., a number related to damage associated withan insured vehicle) into the application running on the mobile device.To generate a claim number, a claimant may contact an entity managingenhanced claims processing server 101 (e.g., an insurance company, etc.)with a first notice of loss (FNOL). The claimant may contact theinsurance company in any number of ways, including via agent, by phone,by email, via a company website, etc. As part of the FNOL, the claimantmay provide basic identifying and/or validating information (e.g., name,age, claim number, etc.) and vehicle information, including the make,model, and year of manufacture. The claimant may also provide thegeneral areas of damage to the vehicle and any other relevant details(e.g., condition of glass, under carriage, engine, wheels, airbags, etc.associated with the vehicle). In one embodiment, this information may beprovided by the claimant from a remote location (e.g., location of anaccident, claimant's home, agent's office, etc.) using the applicationloaded onto the mobile device, or any other suitable application.

The mobile device may then transmit the entered claim number and relatedinformation to server 101. Server 101 may determine if the claim requestis valid by, for example, validating the received claim number. Ifserver 101 determines that the claim number is not valid, then server101 may transmit a message to the mobile device, stating that the claimnumber is invalid and the user may then enter another claim number.

If server 101 determines that the claim request is valid, the processmay move to step 2207 where the mobile device may receive images aboutthe claim event from an imaging device (e.g., a camera operativelyconnected to the mobile device). For instance, once a claim request isvalidated, the running application may be configured to display userinstructions about the types of image data (e.g., photos, video, etc.)that should be captured for any damage associated with the claim event(e.g., vehicle accident). It should also be noted that in someembodiments server 101 may not receive a claim number and theapplication may be configured to proceed in providing user instructionson the types of image data that should be captured without transmittinga claim number. The user may receive instructions on various types ofphotos/video, including photos/video of the entire vehicle, VIN doortag, current odometer reading, and/or the damaged areas. In someaspects, the user may capture image data related to at least twodifferent angles of the damage for each panel (e.g., hood, fender, door,bumper, etc.) based on an initial claim description.

The user of the mobile device may use a camera associated with themobile device to take the photos and/or video and transmit these photosand/or video to the server 101 (step 2209). The user may be allowed topreview each photo before selecting the image. Once a photo has beenselected, the image may be shown on a display associated with the mobiledevice under a photo type (e.g., a photo of the entire vehicle, VIN doortag, current odometer reading, and/or damaged area). If the user is notsatisfied with any photo, the user may delete the photo by selecting itand then retake the photo. In some aspects, the user may annotate thephotos (e.g., by drawing a line from one end of the dent to the other,etc.) prior to transmitting them to server 101. In yet otherembodiments, server 101 may itself annotate any received photos/video.

In some embodiments, any approved photo may not be sent to server 101until all of the images have been captured. In some aspects, server 101may support a website interface through which photos may be uploaded bya user of a mobile device. Also, the use of multiple photos (e.g., viastereoscopic techniques), video (e.g., by walking around the vehicle togenerate a complete view), and/or three-dimensional photos/video mayassist in determining the depth of damage to a vehicle. In some aspects,determining the depth of damage may help in classifying the damage(e.g., a turbulent dent versus a dish dent). In addition, the degree ofdamage by area and depth may be automatically estimated through toolssimilar to ultrasound tools. Knowing the depth of damage may also assistin automatically determining the cost of repair or replacement. Inaddition, as the user is taking video/photos of damage associated withthe insured vehicle, a claims adjuster associated with an entitymanaging server 101 (e.g., an insurance company) may interface with theuser in real-time (e.g., via messaging, phone, email, etc.) as thephotos are being sent to the adjuster and/or as the video is beingstreamed to the adjuster and describe to the user the photos/video thatstill need to be taken and/or where to place a camera as thephotos/video are captured.

After server 101 receives image data transmitted from a mobile device instep 2209, server 101 (or an individual/group associated with the entitymanaging server 101) may determine if the photos are acceptable and themobile device may receive, from server 101, a message indicating theacceptability of the photos in step 2211. For instance, server 101 maydetermine that the photos are too blurry and/or that the photos do notcapture the correct angles to clearly show damage associated with theinsured vehicle. If the mobile device receives a message that indicatesthe photos are not acceptable, the process may move to step 2213 wherethe server 101 may send the user instructions on what types of photos totake and/or what changes need to be made to the previously submittedphotos. In this example, the process may move from step 2213 back tostep 2207, where the user may take or retake photos in accordance withthe received instructions.

In yet other embodiments, a dispatcher associated with an entitymanaging server 101 (e.g., an insurance company) may determine ifsubmitted photos are acceptable. In other embodiments, the mobile devicemay itself determine if any given photo is blurry and/or inaccurate andprompt the user to retake the photo. In this aspect, the application fordamage assessment and claims processing running on the mobile device mayhave computer-executable instructions stored within a memory of themobile device for automatically detecting and/or rejecting a photo/videocaptured within a given category.

If the mobile device receives a message that indicates the photos areacceptable, the process may move to step 2215 where the mobile devicemay receive confirmation from server 101 that the claim request iscomplete. For example, the mobile device may receive a message fromserver 101 indicating that the claim request has been successfullycompleted.

FIGS. 23-31 show display screens displayed to a user of a mobile devicein accordance with some aspects of the disclosure. The display screensmay be used to implement a process similar to the process described inFIG. 22. In some embodiments, one or more display screens described inthe disclosure may be combined and/or may be used in combination.

FIG. 23 shows a display screen displayed to a user of a mobile device inaccordance with at least one aspect of the present disclosure. Screen2301 shows an initial display screen displayed when a user launches adamage assessment and claims processing application stored on a mobiledevice (e.g., network device 201) in accordance with at least one aspectof the present disclosure. In certain aspects, a user may have aplurality of claim estimates pending, where the claims may be at variousstages of completion. For example, screen 2301 displays that userinterface element 2301 a is associated with a first claim, and the claimstatus is indicated as “in progress.” Accordingly, element 2301 a may beselected so that the first claim may be completed by the user. Userinterface element 2301 b is associated with a second claim, and theclaim status is indicated as “completed.” Accordingly, element 2301 amay not be selectable, as the claims has already been completed. The“Start a New Estimate” button 2301 c on screen 2301 may be selected inorder to start a new claim estimate.

FIG. 24 shows a display screen displayed to a user of a mobile device inaccordance with at least one aspect of the present disclosure. Screen2401 shows an initial display screen displayed when a user starts a newclaim estimate with the application in accordance with at least oneaspect of the present disclosure. For example, screen 2401 may bedisplayed when button 2301 c of FIG. 2301 is selected.

Screen 2401 displays various stages for the claim estimate. Userinterface element 2401 a may be associated with a “Damaged Areas” stage,user interface element 2401 b may be associated with a “Car” stage, userinterface element 2401 c may be associated with a “Vehicle ID” stage,and user interface element 2401 d may be associated with an “EstimateInformation” stage. In certain aspects, these user interface elementsmay be selectable based on the status of the claim estimate. Forexample, element 2401 b may be selectable, and upon selection, the usermay be guided to complete the “Damaged Areas” stage of the claimestimate. However, elements 2401 b, 2401 c, and 2401 d may not beselectable until the “Damaged Areas” stage is completed. A “Submit forEstimate” button 2401 e on screen 2401 may be inactive until each of thestages is completed. In certain aspects, the claim estimate may compriseadditional stages, one or more described stages may be omitted, and/oran order for the stages may be any suitable order or the stages may beunordered.

FIG. 25 shows display screens displayed to a user of a mobile device inaccordance with at least one aspect of the present disclosure. Screens2501, 2503, 2505, and 2507 show instruction display screens displayed toa user in accordance with at least one aspect of the present disclosure.For example, screens 2501, 2503, 2505, and 2507 may be displayed when auser selects element 2401 a of FIG. 24, and the user is guided tocomplete the “Damaged Areas” stage of the claim estimate. Screens 2501a, 2503 a, 2505 a, and 2507 a may comprise frames that displayinstructions to the user on how to complete the “Damaged Areas” stage ofthe claim estimate. A user may scroll from screen 2501 a to screen 2503a, and so on, with a gesture that interacts with the display of themobile device, such as a finger swipe. Upon reaching the conclusion ofthe instructions for the “Damaged Areas” stage of the claim estimate,the user may be directed to a screen for taking photos and/or video ofthe damaged areas for the vehicle. For instance, the user may bedirected to a screen similar to screen 507 of FIG. 5 a.

In certain aspects of the disclosure, the application may instruct theuser to take several photos of damaged areas on a vehicle, as describedabove. The user may be prompted to preview and approve the photos. Ifthe user does not approve of the photo, the photo may be retaken. In anexample, the user may be instructed to take at least three photos ofeach damaged area. In this example, one or more screens may instruct theuser to take three photos of a first damaged area. Once three photoshave been taken and have been approved by the user for the first damagedarea, the application may proceed by asking the user if there areadditional damaged areas. If the user indicates an additional damagedarea, the application may direct the user to a plurality of screens thatinstruct the user to take at least three photos of the additionaldamaged area. Once three photos have been taken and have been approvedby the user for the additional damaged area, the application may proceedby again asking the user if there are additional damaged areas. If theuser indicates that there are no additional damaged areas, theapplication may direct the user to the next stage of the claim estimate.For example, the user may be directed to the “Car” stage of the claimestimate. In another embodiment, the user may be directed to a screensimilar to screen 2401 of FIG. 24, and element 2401 b may be selectablebecause the “Damaged Areas” stage of the claim estimate has beenpreviously completed. In this embodiment, the user may select element2401 b and may further be directed to complete the “Car” stage of theclaim estimate.

FIG. 26 shows display screens displayed to a user of a mobile device inaccordance with at least one aspect of the present disclosure. Screens2601 and 2603 show instruction display screens displayed to a user inaccordance with at least one aspect of the present disclosure. Forexample, screens 2601 and 2603 may be displayed when a user selectselement 2401 b of FIG. 24, and the user is guided to complete the “Car”stage of the claim estimate. Screens 2601 a and 2603 a may compriseframes that display instructions to the user on how to complete the“Car” stage of the claim estimate. A user may scroll from screen 2601 ato screen 2603 a with a gesture that interacts with the display of themobile device, such as a finger swipe. Upon reaching the conclusion ofthe instructions for the “Cars” stage of the claim estimate, the usermay be directed to a screen for taking photos and/or video of thedamaged areas for the vehicle. For instance, the user may be directed toa screen similar to screen 507 of FIG. 5 a.

In certain aspects of the disclosure, the application may instruct theuser to take several photos of the vehicle, as described above. The usermay be prompted to preview and approve the photos. If the user does notapprove, the photo may be retaken. In an example, the user may beinstructed to take at least four photos of the vehicle, each from adifferent angle. In this example, one or more screens may instruct theuser to take the four photos of the vehicle. Screen 2701 may comprise adisplay screen where the user may select to take a photo of the vehicle.Screen 2701 may allow the user to select button 2703 a to start thecamera functionality within the mobile device and the “Cancel” button2703 b may be selected to cancel out of Screen 2701.

In an embodiment, when a user selects button 2703 a in screen 2701, themobile device may display a shutter screen to indicate that a photo isbeing taken. When a user selects button 2703 c a photo that has beentaken may be reviewed, as previously described. In some aspects of thedisclosure, screen 2701 a comprises a display portion of screen 2701that displays a view finder for a camera functionality within the mobiledevice. For example, the image displayed on screen 2701 a may indicatethe picture that will be taken when button 2703 a is selected. Screen2701 a may include on or more guides 2701 b. For example, screen 2701 adisplays guides for orienting a user that is taking a picture from anangle that captures the front and driver-side portions of a vehicle. Inaspects of the disclosure, screen 2701 a may include guides for takingpictures of a vehicle from various angles, for taking pictures of acertain portions of a vehicle, for instance pictures of damaged portionsor pictures of a VIN number, or for any other suitable purpose.

Once the photos of the vehicle from various angles have been taken andhave been approved by the user, the application may direct the user tothe next stage of the claim estimate. For example, the user may bedirected to the “Capture Vehicle ID” stage of the claim estimate. Inanother embodiment, the user may be directed to a screen similar toscreen 2401 of FIG. 24, and element 2401 c may be selectable because the“Damaged Areas” stage and the “Car” stage of the claim estimate havebeen previously completed. In this embodiment, the user may selectelement 2401 c and may further be directed to complete the “CaptureVehicle ID” stage of the claim estimate.

FIG. 28 shows display screens displayed to a user of a mobile device inaccordance with at least one aspect of the present disclosure. Screens2801 and 2803 show instruction display screens displayed to a user inaccordance with at least one aspect of the present disclosure. Forexample, screens 2801 and 2803 may be displayed when a user selectselement 2401 c of FIG. 24, and the user is guided to complete the“Capture Vehicle ID” stage of the claim estimate. Screens 2801 a and2803 a may comprise frames that display instructions to the user on howto complete the “Capture Vehicle ID” stage of the claim estimate. A usermay scroll from screen 2801 a to screen 2803 a with a gesture thatinteracts with the display of the mobile device, such as a finger swipe.Upon reaching the conclusion of the instructions for the “CaptureVehicle ID” stage of the claim estimate, the user may be directed to ascreen for taking photos and/or video of the damaged areas for thevehicle. For instance, the user may be directed to a screen similar toscreen 507 of FIG. 5a . In some embodiments, the vehicle ID may beentered by the user, for example, using one or more text input fieldsincluded in the application.

Once the vehicle ID has been entered, the application may direct theuser to the next stage of the claim estimate. For example, the user maybe directed to the “Enter Claim Information” stage of the claimestimate. In another embodiment, the user may be directed to a screensimilar to screen 2401 of FIG. 24, and element 2401 d may be selectablebecause the “Damaged Areas” stage, the “Car” stage, and the “EnterVehicle ID” stage of the claim estimate have been previously completed.In this embodiment, the user may select element 2401 d and may furtherbe directed to complete the “Enter Claim Information” stage of the claimestimate.

FIG. 29 shows a display screen displayed to a user of a mobile device inaccordance with at least one aspect of the present disclosure. Screen2901 shows an input display screen displayed to a user in accordancewith at least one aspect of the present disclosure. For example, 2901may be displayed when a user selects element 2401 d of FIG. 24, and theuser is guided to complete the “Enter Claim Information” stage of theclaim estimate. Screen 2901 may comprise text fields that may be used toinput claim information to the application. For example, screen 2901 maycomprise one or more text input fields 2901 a used to input a name forthe claim and text input field 2901 b used to input a claim number forthe claim. In some embodiments, claim information may be omitted and anysuitable identification information used to identify the claimant can beused.

Once the claim information has been entered, the application may directthe user to the next stage of the claim estimate. For example, the usermay be asked to submit the completed estimate. In an embodiment, theuser may be directed to a screen similar to screen 2401 of FIG. 24, andelement 2401 e may be selectable because the “Damaged Areas” stage, the“Car” stage, the “Enter Vehicle ID” stage, and the “Enter ClaimInformation” stage of the claim estimate have been previously completed.In this embodiment, the user may select element 2401 e and theapplication may accordingly submit the claim estimate for processing.

In some aspects of the disclosure, once a claim has been submitted forprocessing, one or more portions of the application may be locked. FIG.30 shows a display screen displayed to a user of a mobile device inaccordance with at least one aspect of the present disclosure. Screen3001 may be similar to screen 2401 of FIG. 24, as described above. In anembodiment, screen 3001 may display locked portions of the application.For example, User interface element 3001 a may be associated with a“Damaged Areas” stage, user interface element 3001 b may be associatedwith a “Car” stage, user interface element 3001 c may be associated witha “Vehicle ID” stage, and user interface element 3001 d may beassociated with a “Estimate Information” stage, and, in some aspects ofthe disclosure, one or more of these elements may not be selectablebecause one or more of the stages for the claim estimate may be locked.Display 3001 may indicate that one or more stages are locked bydisplaying a lock, or any other suitable indication, next to the userinterface element corresponding to the stage. In addition, userinterface element 3001 e may also be locked based on the submission ofthe claim estimate.

In some aspects of the disclosure, the claim estimate may be submittedto, for example, server 101 for processing. The processing may include areview of the submitted claim estimate, such as a review of theinformation submitted for the claim estimate and the photos and/orvideos submitted for the claim estimate. In an embodiment, the reviewmay comprise a user reviewer that reviews the submitted claim estimate.

In some embodiments, a review may determine that one or more portions ofthe submitted claim estimate are unacceptable. For example, a review maydetermine that one or more submitted photos for the claim estimate areunacceptable, as described above. The photos may be unacceptable basedon a determination that they are blurry, they do not capture the damage,they were not taken in accordance with instructions, or any othersuitable considerations. In some aspects of the disclosure, server 101may send one or more messages to the mobile device about the claimestimate.

FIG. 31 shows display screens displayed to a user of a mobile device inaccordance with at least one aspect of the present disclosure. Screens3101 and 3103 show messaging display screens displayed to a user inaccordance with at least one aspect of the present disclosure. Forexample, screens 3101 and 3103 may be displayed when a mobile devicereceives a message about a submitted claim estimate. Screen 3101 maycomprise user interface element 3101 a, that indicates one or moremessages have been received. The user may select element 3101 a tolaunch a messaging display such as screen 3103. Screen 3103 may displayone or more message to a user. For example, screen 3103 displays message3103 a and 3103 b. Message 3103 b may comprise a message that instructsthe user to take additional actions for the claim estimate. In thisexample, message 3103 b instructs the user to retake a car photo fromthe angle of the rear passenger and a damage photo of the rear bumper.

In some aspects, based on a received message that instructs the user totake additional photos, one or more portions of a locked application maybe unlocked. For example, based on received message 3103 b, userinterface element 3101 b and user interface element 3101 c may beselectable. Selecting user interface element 3101 b may direct a user tothe “Damages” stage of the claim estimate so that one or more damagesphotos may be taken. Selecting user interface element 3101 b may directa user to the “Car” stage of the claim estimate so that one or morevehicle photos may be taken. Accordingly, based on received message 3103b, the “Damages” stage and/or the “Car” stage of the claim estimate maybe unlocked.

In an embodiment, message 3103 b may include button 3103 c that guidesthe user to take the one or more photos that message 3103 b instructsthe user to take. For example, selecting button 3013 c may guide theuser to one or more the “Damages” stage of the claim estimate and/or the“Car” stage of the claim estimate so that the user may take additionalphotos.

Once the user takes the additional photos, the user may submit the claimestimate. In an embodiment, the user may be directed to a screen similarto screen 2401 of FIG. 24, and element 2401 e may be selectable becausethe “Damaged Areas” stage, the “Car” stage, the “Enter Vehicle ID”stage, and the “Enter Claim Information” stage of the claim estimatehave been previously completed. For example, the additional photosrequest in a received message may have been taken. In this embodiment,the user may select element 2401 e and the application may accordinglysubmit the claim estimate for processing.

In some aspects of the disclosure, once a claim has been submitted forprocessing, one or more portions of the application may be re-locked.For example, a screen similar to screen 3001 of FIG. 30 may be displayedto the user. After received message 3103 b of FIG. 31 unlocked portionsof the application, such as the “Damages” stage of the claim estimateand the “Car” stage of the claim estimate, these portions may bere-locked based on the newly submitted claim estimate.

FIG. 32 shows an annotation process 3200 in accordance with at least oneaspect of the present disclosure. In certain aspects, a mobile device(e.g., iPad™, iPhone™ Android™, etc.) may transmit data to a server,such as server 101, to facilitate one or more steps of the process inFIG. 32. For example, a mobile device that implements the process ofFIG. 22 may interact with a server that implements the process of FIG.3. The transmitted data may comprise photos and/or video of an insureditem (e.g., a vehicle). The process of FIG. 32 may be implemented toannotate and/or alter photos and/or video received about the insureditem. In an example, server 101, terminal 141, and/or terminal 151 mayimplement the process of FIG. 32. In some aspects of the disclosure, thedevice implementing the process of FIG. 32 may comprise a multi-touchscreen (e.g., a tablet computer).

The process of FIG. 32 may start out at step 3201 where a device (e.g.,server 101, terminal 141, and/or terminal 151) may receive data (e.g.,photos and/or video) about an insured item (e.g., a vehicle). In anexample, the data may be received based on the processes of FIG. 3and/or FIG. 22. In some aspects of the disclosure, the data may comprisephotos of a vehicle that has been involved in an accident.

The process may then move to step 3203 where the device displays thedata to a user. For example, a device (e.g., server 101, terminal 141and/or terminal 151) may display received data (e.g., photos and/orvideo) to a user. In an example, the user may comprise a claimsprocessor, an administrator, or any other suitable user.

The process may then move to step 3205 where the device displays altereddata to a user. For example, a device (e.g., server 101, terminal 141and/or terminal 151) may display altered data (e.g., photos and/orvideo) to a user (e.g., claims processor, administrator, and the like).In an example, the altered data may comprise the received photos and/orvideos that have been altered, for example, by the user. As describedbelow, displaying altered data may comprise displaying a received photousing one or more lenses that alter the photo (e.g. a zoom lens, acontrast lens, a tint lens, bright lens, and the like).

The process may then move to step 3207 where the device receivesannotations about the received data. For example, a device (e.g., server101, terminal 141 and/or terminal 151) may receive annotations aboutdata (e.g., photos and/or video) from a user (e.g., claims processor,administrator, and the like). In an example, the annotations maycomprise annotations about received photos and/or videos. In someaspects of the disclosure, the annotations may comprise data aboutdamage to an insured item (e.g., a vehicle) displayed in a receivedphoto. As described below, the annotations may comprise damage data andmay further include a severity for the damage, a type for the damage,and an impact for the damage. The process may then move to step 3209where the device displays the annotated data to the user. For example,the device may display a received photo to the user, and the device mayalso display received annotations about the photo along with the photo(e.g., on top of the photo and/or near the photo) to the user.

In some aspects of the disclosure, the device implementing the processof FIG. 32 may comprise a multi-touch screen (e.g., a tablet computer)and alterations to the data and/or annotations about the data may bereceived from the user via the multi-touch screen. In some embodiments,the process of FIG. 32 may comprise additional steps, may omit describedsteps, and/or may be performed in a different order.

FIG. 33 shows a display screen displayed to a user of a device inaccordance with at least one aspect of the present disclosure. Screen3301 shows an annotation display screen displayed to a user inaccordance with at least one aspect of the present disclosure. Forexample, screen 3301 may display photo 3301 a, such as a photo about aninsured item (e.g., a vehicle). Photo 3301 a may comprise a photo of avehicle that has been in an accident may show damage to the vehicle. Inan embodiment, annotations 3303 a and 3303 b may comprise damageannotations that indicate the damage displayed at a portion of thephoto. Annotations 3305 a and 3305 b may comprise descriptions fordamage annotations, such as damage annotations 3303 a and 3303 b.

In an embodiment, damage annotation 3303 a may indicate damage at aportion of photo 3301 a and annotation 3305 a may describe the damageindicated by damage annotation 3303 a. In this example, damageannotation 3303 a comprises a dent of high severity, as described byannotation 3305 a. In another example, damage annotation 3303 b mayindicate damage at a portion of photo 3301 a and annotation 3305 b maydescribe the damage indicated by damage annotation 3303 b. In thisexample, damage annotation 3303 b comprises a scrape of medium severity,as described by annotation 3305 b.

In certain aspects of the disclosure, the damage annotations displayedin FIG. 33 may be generated using a touch display, such as a tablet, atouch screen laptop, or any other suitable device. For example, adisplay similar to the displays illustrated in FIGS. 34 through 35.

FIG. 34 shows display screens in accordance with at least one aspect ofthe present disclosure. Screen 3401 shows an annotation display screenthat may receive input from a user in accordance with at least oneaspect of the present disclosure. For example, screen 3401 may displayto a user a screen similar to screen 3301 of FIG. 33. A user mayinteract with screen 3401, for example by touch, to input an annotation,as described above with reference to FIG. 33.

In an embodiment, once a user touches the display, a display screen suchas screen 3403 may be displayed. For example, one or more interfaces,such as interfaces 3403 a, 3403 b, 3403 c, and 3403 d may be displayed.Interface 3403 a may comprise a damage interface that indicates a damageannotation. Interfaces 3403 b, 3403 c, and 3403 d may compriseinterfaces that allow input of additional damage information. Forexample, a user may select interface 3403 b to input severityinformation, 3403 c to input type information, and 3403 d to inputimpact information. A user may select an interface by touching thedisplay.

In an example, when a user selects the type interface 3403 c, a displayscreen such as screen 3405 may be displayed to the user. For example,one or more interfaces, such as interfaces 3405 a, 3405 b, 3405 c, and3405 d may be displayed. Interfaces 3405 a, 3405 b, 3405 c, and 3405 dmay comprise interfaces that allow input of additional damageinformation about the type of damage. For example, a user may selectinterface 3405 a to indicate a dent type damage, 3405 b to indicate acrack type damage, 3405 c to indicate a scratch type damage, and 3405 dto indicate a break type damage. In some embodiments, any other suitableinterfaces that indicate any suitable damage type may be included.

In an example, when a user selects the crack interface 3405 b, a displayscreen such as screen 3407 may be displayed to the user. For example,one or more interfaces, such as interfaces 3403 a, 3403 b, 3403 c, and3403 d may be displayed. Interface 3403 a may comprise a severityinterface that indicates a severity for the damage annotation.Interfaces 3407 b, 3407 c, and 3407 d may comprise interfaces that allowinput of additional information about the severity of the damage. Forexample, a user may select interface 3407 b to indicate low severity,3407 c to indicate medium severity, and 3407 d to indicate highseverity. In some embodiments, any other suitable interfaces thatindicate any suitable damage severity may be included.

In an example, a user may select type interface 3403 c from displayscreen 3403, crack interface 3405 b from display screen 3405, andseverity interface 3407 d from display screen 3407 to indicate a highseverity. In this example, a damage annotation may be generated, wherethe annotation comprises a crack type damage with a high severity.

FIG. 35 shows a display screen in accordance with at least one aspect ofthe present disclosure. Screen 3501 shows an annotation display screenthat may receive input from a user in accordance with at least oneaspect of the present disclosure. For example, screen 3501 may displayto a user a screen similar to screen 3301 of FIG. 33. A user mayinteract with screen 3501, for example by touch, to input an annotation,as described above with reference to FIG. 33.

In an embodiment, once a user touches the display, a display screen suchas screen 3501 may be displayed. For example, one or more interfaces,such as interfaces 3501 a, 3501 b, 3501 c, and 3501 d may be displayed.Interface 3501 a may comprise a damage interface that indicates a damageannotation. Interfaces 3501 b, 3501 c, and 3503 d may compriseinterfaces that allow input of additional damage information. Forexample, a user may select interface 3501 b to input severityinformation, 3501 c to input type information, and 3501 d to inputimpact information. In some embodiments, a user may select an interfaceby touching the display with a member, such as a finger, and holding themember on the display until interfaces 3501 a, 3501 b, 3501 c, and 3501d are displayed, for example, by the device. Interface 3501 a may bedisplayed near the member, and the user may drag the member to one ofinterfaces 3501 b, 3501 c, and 3501 d to select the interface.

In an example, when a user selects the severity interface 3501 b, adisplay screen such as screen 3503 may be displayed to the user. Forexample, one or more interfaces, such as interfaces 3503 a, 3503 b, and3503 c may be displayed. Interfaces 3503 a, 3503 b, and 3503 c maycomprise interfaces that allow input of additional damage informationabout the severity of damage. Here the interfaces may be displayed asconcentric circles, as shown in FIG. 35, and the user may drag a memberto the corresponding concentric circle to select a severity (e.g., low,medium, high). In some embodiments, any other suitable interfaces thatindicate any suitable damage type may be included.

FIG. 36 shows a display screen displayed to a user of a device inaccordance with at least one aspect of the present disclosure. Screen3601 shows an annotation display screen displayed to a user inaccordance with at least one aspect of the present disclosure. Screen3601 may be similar to screen 3301 of FIG. 33. For example, screen 3601may display photo 3601 a, such as a photo about an insured item (e.g., avehicle). In this example, the displayed photo 3601 a may be related tothe displayed photos 3301 a. For instance, photos 3301 a and 3601 a maydisplay photos from the same event (e.g., an accident) and of the sameinsured item (e.g., a vehicle). Photos 3301 a and 3601 a comprise photosfrom different angles of the insured item and may display variousdamages to the insured item. In an embodiment, annotations 3603 a and3603 b may comprise damage annotations that indicate the damagedisplayed at a portion of the photo. Annotations 3605 a and 3605 b maycomprise descriptions for damage annotations, such as damage annotations3603 a and 3603 b.

FIG. 37 shows a display screen displayed to a user of a device inaccordance with at least one aspect of the present disclosure. Screen3701 shows an annotation display screen displayed to a user inaccordance with at least one aspect of the present disclosure. Screen3701 may be similar to screen 3301 and 3601. For example, screen 3701may display photo 3701 a, such as a photo about an insured item (e.g., avehicle). In this example, the displayed photo 3701 a may be related tothe displayed photos 3301 a and 3601 a. For instance, photos 3301 a,3601 a, and 3701 a may display photos from the same event (e.g., anaccident) and of the same insured item (e.g., a vehicle). Photos 3301 a,3601 a, and 3701 a may comprise photos from different angles of theinsured item and may display various damages to the insured item. In anembodiment, annotation 3703 a may comprise a damage annotation thatindicates the damage displayed at a portion of the photo. Annotations3705 a may comprise descriptions for damage annotations, such as damageannotations 3703 a.

In an embodiment, damage annotation 3703 a may indicate damage at aportion of photo 3701 a. For example, a damage annotation may begenerated using one or more screens of FIGS. 34 and 35. In this example,damage annotation 3703 a comprises a crack of high severity, asdescribed by annotation 3705 a. Screens 3301 a and 3601 a may also showdamage annotations related to, for example, an insured item displayed inphoto 3701 a.

In an embodiment, one or more photos displayed to a user may be altered.FIG. 38 shows a display screen displayed to a user of a device inaccordance with at least one aspect of the present disclosure. Screen3801 shows an annotation display screen displayed to a user inaccordance with at least one aspect of the present disclosure. Screen3801 may be similar to screen 3301 of FIG. 33. For example, screen 3801may display photo 3801 a, such as a photo about an insured item (e.g., avehicle). Screen 3801 may also display an interface, such as a lens,that alters the display of photo 3801 a. In this example, interface 3803a comprises a lens interface that adjusts the brightness of displayedphoto 3801 a. Accordingly, a portion of photo 3801 a may be displayedwith a first brightness, and the portion of photo 3801 a displayedwithin lens 3803 a may be displayed with a second brightness differentfrom the first brightness, where the second brightness is based on howinterface 3803 a is configured.

In an embodiment, a lens may be generated using interface 3803 b.Interface 3803 b may comprise elements 3805 a, 3805 b, 3805 c, and 3805d. For example, a user may select one of elements 3805 a, 3805 b, 3805c, and 3805 d with a member, for example a finger, by touching thedisplay. The user may then drag from interface 3803 b to photo 3801 a togenerate an interface similar to interface 3803 a, such as a lens. In anembodiment, interface 3805 a may be selected to generate a contrastinterface. A contrast interface may display the portion of photo 3801 adisplayed within the contrast interface with a different contrast,similar to interface 3803 a. In an embodiment, interface 3805 b may beselected to generate a brightness interface, similar to interface 3803a. In an embodiment, interface 3805 c may be selected to generate a tintinterface. A tint interface may display the portion of photo 3801 adisplayed within the tint interface with a different tint, similar tointerface 3803 a. In an embodiment, interface 3805 d may be selected togenerate a zoom interface. A zoom interface may display the portion ofphoto 3801 a displayed within the zoom interface with a different zoom,similar to interface 3803 a.

FIG. 39 shows a display screen displayed to a user of a device inaccordance with at least one aspect of the present disclosure. Screen3901 shows an annotation display screen displayed to a user inaccordance with at least one aspect of the present disclosure. Screen3901 may be similar to screen 3801. For example, screen 3901 may displayphoto 3901 a, such as a photo about an insured item (e.g., a vehicle).Screen 3901 may display a plurality of interfaces 3903 a and 3903 b thatcomprise lens interfaces. In this example, interface 3903 a comprises azoom interface, and the portion of photo 3901 a displayed within thelens interface displays photo 3901 a with a different zoom, aspreviously described. Interface 3903 b comprises a tint interface, andthe portion of photo 3901 a displayed within the tint interface displaysphoto 3901 a with a different tint, as previously described.

In an embodiment, lens interfaces 3903 a and 3903 b may overlap suchthat a portion of photo 3901 a is displayed within both interfaces 3903a and 3903 b. In this example, the portion of photo 3901 a that isdisplayed within both interfaces 3903 a and 3903 b may displayed with adifferent zoom and a different tint. Accordingly, the effect of bothlens interfaces 3903 a and 3903 b may be applied to the portion of photo3901 a that is displayed within the interfaces.

In an embodiment, a user may select an interface, such as a lensinterface, and a menu may be displayed to configure the interface. FIG.40 shows an example lens interface in accordance with at least oneaspect of the present disclosure. Lens interface 4001 comprises a menuto configure the lens interface in accordance with at least one aspectof the present disclosure. Elements 4001 a, 4001 b, 4001 c, and 4001 dmay be selected in order to alter the effect of the lens interface(e.g., display a portion of a photo with a different contrast,brightness, tint, or zoom). Elements 4001 e and 4001 f may be selectedto adjust the size of the lens interface. For example, one or more ofelements 4001 e and 4001 f may be selected by a user with a member, forexample a finger, by touching the display and the elements may bedragged to enlarge or shrink the lens interface.

Element 4001 g may be selected to enlarge the lens to full screen mode.In this embodiment, a full screen lens may adjust the display of aphoto, such as photo 3901 a, such that the effect of the lens isdisplayed across the entire photo. For example, a tint lens may bedisplayed, where a portion of photo 3901 a may be displayed with a firsttint, and a portion of photo 3901 a displayed within a tint lens, suchas lens 3903 b, may be displayed with a second tint different from thefirst tint. When a tint lens such as lens 3903 a is enlarged to fullscreen mode, the entire portion of photo 3901 a may be displayed withthe second tint. In this example, another lens, such as lens 3903 a, mayalso be displayed, and the portion of photo 3901 a displayed within lens3903 a when tint lens 3903 b is in full screen mode may comprise theeffect of both 3903 a and 3903 b, such as when lenses overlapped asdescribed above.

FIG. 41 shows a display screen displayed to a user of a device inaccordance with at least one aspect of the present disclosure. Screen4101 shows an annotation display screen displayed to a user inaccordance with at least one aspect of the present disclosure. Screen4101 may be similar to screen 3901. For example, screen 4101 may displayphoto 4101 a, such as a photo about an insured item (e.g., a vehicle).Screen 4101 may display interface 4103 a that comprises a lensinterface. In this example, interface 4103 a comprises a zoom interface.For interface 4103 a, a portion of photo 4101 a may be displayed with afirst zoom, and the portion of photo 4101 a displayed within lens 4103 amay be displayed with a second zoom different from the first zoom, wherethe second zoom is based on how interface 3803 a is configured. In thisexample, the effect of zoom lens 4103 a, that is the second zoom, may beadjusted by a user. In an embodiment, a user may select the insideportion of interface 4103 a with a member, for example a finger, bytouching the display. The user may then select outside of interface 4103a using a second member, for example a finger, by touching the display.The user may then drag the second member to adjust the effect ofinterface 4103 a. In this example, the user may drag the second memberup to increase the zoom effect and drag the second finger down todecrease the zoom effect of interface 4103 a.

In an embodiment, the user may be displayed altered photos of, forexample, an insured item, and may further generate one or moreannotations based on the altered photos. Accordingly, a user may viewone or more photos according to FIGS. 38-41 and may further generatedamage annotations, as described above.

FIG. 42 shows an annotation process 4200 in accordance with at least oneaspect of the present disclosure. In certain aspects, a mobile device(e.g., iPad™, iPhone™ Android™, etc.) may transmit data to a server,such as server 101, to facilitate one or more steps of the process inFIG. 42. For example, a mobile device that implements the process ofFIG. 22 may interact with a server that implements the process of FIG.3. The transmitted data may comprise photos and/or video of an insureditem (e.g., a vehicle). The process of FIG. 42 may be implemented togenerate an estimate about an insured item, such as a vehicle. In anexample, server 101, terminal 141, and/or terminal 151 may implement theprocess of FIG. 42. In some aspects of the disclosure, the deviceimplementing the process of FIG. 42 may comprise a multi-touch screen(e.g., a tablet computer).

In an embodiment, the process of FIG. 32 may be used in combination withthe process of FIG. 42. For example, a user may annotate photos of aninsured item based on the process of FIG. 32. Based on the annotatedphotos, an estimate may be generated for the insured item.

The process of FIG. 42 may start out at step 4201 where a device (e.g.,server 101, terminal 141, and/or terminal 151) may receive data (e.g.,photos and/or video) about an insured item (e.g., a vehicle). In anexample, the data may be received based on the processes of FIG. 3, FIG.22, and/or FIG. 32. In some aspects of the disclosure, the data maycomprise photos of a vehicle that has been involved in an accident. Insome embodiments, the received photos may comprise annotations.

The process may then move to step 4203 where the device displays thedata to a user. For example, a device (e.g., server 101, terminal 141and/or terminal 151) may display received data (e.g., photos and/orvideo) to a user. In an example, the user may comprise a claimsprocessor, an administrator, or any other suitable user.

The process may then move to step 4205 where the device receivesestimate data about the insured item. For example, a device (e.g.,server 101, terminal 141 and/or terminal 151) may receive estimate dataabout an insured item (e.g. a vehicle) from a user (e.g., claimsprocessor, administrator, and the like). In an example, the estimatedata may be received based on one or more photos being displayed to theuser. In some embodiments, the displayed photos may be displayed withone or more annotations, and the estimate data may be based on the oneor more annotations. The received estimate data may comprise datarelated to a cost for repairing damage to the insured item and/orreplacing portions of the insured item. For example, the receivedestimate data may be data about a damaged part or portion of the insureditem.

The process may then move to step 4207 where the device calculates anestimate based on the received estimate data. For example, a device(e.g., server 101, terminal 141 and/or terminal 151) may receiveestimate data about an insured item and calculate an estimate based onthe received estimate data. In this example, the received estimate datamay comprise data related to a cost for repairing damage to the insureditem and/or replacing portions of the insured item, and the estimate maybe calculated based on this data.

The process may then move to step 4209 where the device displays thecalculated estimate. For example, a device (e.g., server 101, terminal141 and/or terminal 151) may display the calculated estimate to a user(e.g., claims processor, administrator, and the like). In this example,the calculated estimate may comprise an aggregate of estimates for oneor more repairs and/or replacements.

In some aspects of the disclosure, the device implementing the processof FIG. 42 may comprise a multi-touch screen (e.g., a tablet computer)and estimate data may be received from the user via the multi-touchscreen. In some embodiments, the received data may be associated withclaim information. For example, a claim may have been generated for anevent, such as a vehicle accident, and the received data may comprisephotos of a vehicle involved in the accident. The received data may beassociated with generated claim, which may include a customer name, adate for the event, a description for the event, a location for theevent, a location for the customer, a VIN number for the vehicle, apolicy number, and any other suitable claim information. The process ofFIG. 42 may comprise additional steps, may omit described steps, and/ormay be performed in a different order.

FIG. 43 shows a display screen displayed to a user of a device inaccordance with at least one aspect of the present disclosure. Screen4301 shows an estimate display screen displayed to a user in accordancewith at least one aspect of the present disclosure. For example, screen4301 may display photo 4301 a, such as a photo about an insured item(e.g., a vehicle). Photo 4301 a may comprise a photo of a vehicle thathas been in an accident may show damage to the vehicle. In anembodiment, annotations 4303 a and 4303 b may comprise damageannotations that indicate the damage displayed at a portion of thephoto.

In certain aspects of the disclosure, annotations 4304 a and 4303 b mayinclude a type of damage and a severity for the damage. For example,damage annotation 4303 a may indicate damage at a portion of photo 4301a that comprises a dent of high severity. In some embodiments, thedamage annotations may also indicate whether the damage displayed in aphoto comprises incident damage or prior damage. For example,annotations 4304 a may comprise damage related to an incident, such as avehicle accident, while annotation 4304 b may comprise prior damage thatis not related to the incident.

In an embodiment, a damage annotation may be selected and estimate datamay be input based on the selection. For example, a user may select adamage annotation with a member, such as finger, by touching thedisplay. FIG. 44 shows a display screen displayed to a user of a devicein accordance with at least one aspect of the present disclosure. Screen4401 shows an estimate display screen displayed to a user in accordancewith at least one aspect of the present disclosure. For example, screen4401 may display photo 4401 a, such as a photo about an insured item(e.g., a vehicle). In an embodiment, annotations 4303 a and 4303 b maycomprise damage annotations that indicate the damage displayed at aportion of the photo. In an example where damage annotation 4403 a hasbeen selected, interface 4405 a may be associated with damage annotation4403 a and the interface may further receive estimate data about thedamage annotation.

Interface 4405 a may comprise input field 4405 b, where a part locationmay be input. For example, damage annotation 4403 a may be located atthe front of a vehicle, and input field 4405 b may receive this locationinformation. Interface 4405 a may further comprise input field 4405 c,where a part description may be input. For example, a user may determinethat the damage is related to a part, such as a front fender of avehicle, and input field 4405 c may receive this part description.

In some embodiments, a claim may have been generated for an event, suchas a vehicle accident, and photo 4401 a and damage annotation 4403 a and4403 b may be associated with the generated claim. The claim informationmay include a customer name, a date for the event, a description for theevent, a location for the event, a location for the customer, a VINnumber for the vehicle, a policy number, and any other suitable claiminformation.

In some aspects of the disclosure, a device displaying screen 4405(e.g., server 101, terminal 141 and/or terminal 151) may be operativelyconnected to a database (e.g., database 121). The database may storepart information for makes and models for a plurality of cars. In anembodiment, the database may additionally store cost information for oneor more parts, such as the cost for repairing a part and the cost forreplacing a part. For example, the database may store part information,such as a fender type, for a car of a first make and a first model, andthe cost for repairing the fender and the cost for replacing the fender.The cost stored in the database may comprise a cost for parts, parts andlabor, or any other suitable cost.

In some embodiments, based on the claim information, one or more ofinput fields 4405 b and 4405 c may be prepopulated. For example, a makeand model for the vehicle associated with the claim may be determinedbased on the claim information, and the database may be queried todetermine part information for the make and model. Input fields 4405 band 4405 c may comprise drop down menus, and the drop down menus may beprepopulated based on the make and model of the vehicle involved in theclaim. In an example, a vehicle may be of a first make and model, andpart information may be determined for the vehicle.

Interface 4405 a may display a cost for repair and/or replacement of thepart identified in input fields 4405 b and 4405 c. For example, thedatabase may be queried to determine part information, a cost forrepairing the part, and a cost for replacing the part. The cost may bedisplayed and a user may select repairing the part with button 4405 dand replacing the part with button 4405 e.

In an embodiment, estimate data may be input for a damage annotation andthe estimate data may be displayed to a user. FIG. 45 shows a displayscreen displayed to a user of a device in accordance with at least oneaspect of the present disclosure. Screen 4501 shows an estimate displayscreen displayed to a user in accordance with at least one aspect of thepresent disclosure. For example, screen 4501 may display photo 4501 a,such as a photo about an insured item (e.g., a vehicle). In anembodiment, annotations 4503 a and 4503 b may comprise damageannotations that indicate the damage displayed at a portion of thephoto. In an example, damage annotation 4503 a may be selected andestimated data may be received about the damage annotation.

In some aspects of the disclosure, an estimate for damage annotation4503 a may be calculated, and the estimate may be displayed at userinterface element 4505 a. For example, the received estimate data mayindicate a replacement for a front fender of the vehicle involved theaccident. The estimate may include a replacement cost for the parts(e.g., fender and paint) and labor (e.g., installation and painting). Atotal for the estimate may further be displayed. In some aspects of thedisclosure, the cost for parts and/or labor may be queried from adatabase based on associated claim information, as further describedabove.

In some embodiments, a plurality of estimated data may be received abouta plurality of damage annotations, and a plurality of estimates may becalculated. In this example, the plurality of estimates may bedisplayed, for example by element 4505 a, and a total for the cost ofthe plurality of estimates may be displayed. In certain aspects of thedisclosure, the damage annotations and estimates displayed in FIGS.43-45 may be generated using a touch display, such as a tablet, a touchscreen laptop, or any other suitable device.

FIG. 46 shows a damage estimation process 4600 in accordance with atleast one aspect of the present disclosure. In certain aspects, a mobiledevice (e.g., iPad™ iPhone™, Android™, etc.) or any other device, suchas a touch screen device, may transmit data to a server, such as server101, to facilitate one or more steps of the process in FIG. 46. In anexample, a device that implements the process of FIG. 46 may interactwith a server that implements the process of FIG. 3. Transmitted datamay comprise photos, video and/or other metadata of an insured item(e.g., a vehicle). The process of FIG. 46 may be implemented to generatean estimate about an insured item, such as a vehicle. In an example,server 101, terminal 141, and/or terminal 151 may implement the processof FIG. 46. In some aspects of the disclosure, the device implementingthe process of FIG. 46 may comprise a multi-touch screen (e.g., a tabletcomputer).

The process of FIG. 46 may start out at step 4601 where a device (e.g.,server 101, terminal 141, and/or terminal 151) may receive data (e.g.,photos and/or video) about an item (e.g., a vehicle). Examples discussedherein may refer to insured items, but the disclosure is equallyapplicable to items that are not insured and/or insured by third partyentities. In an example, the data may be received based on the processesof FIG. 3, FIG. 22, and/or FIG. 32. In some aspects of the disclosure,the data may comprise photos of a vehicle and/or property that has beeninvolved in an accident. In some embodiments, the received photos maycomprise annotations.

The process may then move to step 4603 where the device displays thedata to a user. For example, a device (e.g., server 101, terminal 141and/or terminal 151) may display received data (e.g., photos and/orvideo) to a user. In an example, the user may comprise a claimsprocessor, an administrator, or any other suitable user. Where thereceived data comprises photos, a plurality of photos may be displayedto the user at the same time.

The process may then move to step 4605 where the device receivesestimate data associated with one or more received photos. For example,a device (e.g., server 101, terminal 141 and/or terminal 151) mayreceive estimate data about an insured item (e.g. a vehicle) from a user(e.g., claims processor, administrator, and the like). In an example,the estimate data may be received based on one or more photos beingdisplayed to the user. The received estimate data may comprise datarelated to a cost for repairing damage to the insured item and/orreplacing portions of the insured item. For example, the receivedestimate data may be data about a damaged part or portion of the insureditem. In an embodiment, the received estimate data may comprise anannotation about one or more of the received photos.

In an embodiment, the received photos may display damage to an insureditem, such as a vehicle, and the received estimate data may be dataabout repairing or replacing the insured item. For example, the receivedestimate data may comprise an annotation that identifies a damaged part,locates the damaged part, and/or includes an estimated amount of laborfor repairing or replacing a damaged part. In some aspects of thedisclosure, loss facts, such as the name of the insured, the date of anevent (e.g., an accident), a description of the event, a location forthe event, a place of residence for the insured, an identificationnumber for an insured item (e.g., a VIN number), a description of theinsured item (e.g., make, model and year of manufacture for a vehicle),a policy number for the insured, and policy facts that define coveragefor the insured may be received along with the received photos. The lossfacts may also be displayed to the user.

The process may then move to step 4607 where the device calculates anestimate based on the received estimate data. For example, a device(e.g., server 101, terminal 141 and/or terminal 151) may receiveestimate data about an insured item and calculate an estimate based onthe received estimate data. In this example, the received estimate datamay comprise data related to a cost for repairing damage to the insureditem and/or replacing portions of the insured item, and the estimate maybe calculated based on the received data.

In an embodiment, the calculated estimate may be calculated based on anannotation that identifies a damaged portion or part of the insureditem, such as a damaged part of a vehicle. For example, an annotationmay be received from a user about damage to a portion or part of aninsured item and the annotation may comprise estimate data for repairingor replacing the damaged portion or part. Accordingly, the calculatedestimate may comprise different costs (e.g., parts cost, labor cost, andany other suitable cost) for repairing that damage or replacing the partindicated by the annotation. The annotation may also specify that acertain part is damaged, but has been deemed to be from a priorincident.

In an embodiment, the estimate may be based on facts known about theinsured item (e.g., make, model, and year of manufacture for a vehicle).For example, received estimate data may indicate damage to the rearbumper for a vehicle of a particular make, model, and year ofmanufacture. In this example, the calculated estimate may be based onthe repair cost for the rear bumper of the vehicle for the particularmake, model, and year of manufacture.

In an embodiment, the device may generate a damage estimate based on aholistic view of a damaged vehicle. Over time, a database may be builtof specific damage templates (e.g., damages to more than one part of avehicle that are commonly associated with one another) andestimated/actual costs for repairing or replacing damages associatedwith these templates. Once this database has been built, damageestimates associated with subsequently analyzed vehicles may begenerated from a holistic view of the vehicles by accessing informationwithin the historical database.

For instance, if a first type of damage to the front bumper of a vehicleis commonly associated with a second type of damage to the headlights ofthe same vehicle and this damage template is associated with apredetermined repair cost in the database, the device may use thisrepair cost to generate a new estimate for subsequent vehicles thatexhibit damage similar to this damage template.

In one example, the damage estimates retrieved from the historicaldatabase may be adjusted based on differences associated with a currentcase. For instance, the damage estimate may be adjusted based on theaverage inflation rate (e.g., for parts, labor, etc.) between the dateat which the damage estimate within the historical database wasgenerated and the current date. In other embodiments, the damageestimate may be adjusted for small differences such as the make, model,and year of manufacture when the vehicle in the historical database andthe currently analyzed vehicle are compared. Similarly, the damageestimate may be adjusted based on differences in the precise damageassociated with the vehicle in the historical database and the damageassociated with the vehicle currently being analyzed. In yet otherexamples, the damage estimate may be adjusted based on the terms of aninsurance policy that covers damage to the insured vehicle currentlybeing analyzed. One of ordinary skill in the art would understand thatany number of factors may be considered when adjusting the damageestimate retrieved for vehicles stored in the historical database tomore accurately reflect a damage estimate for a currently analyzedvehicle.

In an embodiment, the calculated estimate may be based on a labor costassociated with the estimate. For example, the received estimate datamay include a labor duration (e.g., number of labor hours). Thecalculated estimate may include a labor cost estimate that is based onthe labor duration multiplied by a labor cost rate (e.g., cost per hourfor labor). In some aspects of the disclosure, the labor cost rate maydiffer based on a local labor rates for repair work, such as localrepair rates at the location of the event (e.g. accident) or thelocation of the residence of the insured. Labor costs may also differbased on a type of work. For example, body work for a vehicle (e.g.repairing a bumper) may cost a first rate while engine work for avehicle may cost a second rate.

The process may then move to step 4609 where the device displays thecalculated estimate. For example, a device (e.g., server 101, terminal141 and/or terminal 151) may display the calculated estimate to a user(e.g., claims processor, administrator, and the like). The calculatedestimate may be segregated such that the components of the estimate(e.g., part costs, labor costs, and the like) are displayed separately.In this example, a total for the segregated components may also bedisplayed.

In an embodiment, steps 4605 to 4609 may be repeated such that aplurality of annotations that comprise estimate data may be receivedfrom a user. In this example, each annotation may be associated with oneor more received photos and each annotation may indicate damage to aportion or part of an insured item. For instance, where the insured itemcomprises a vehicle, a first annotation may indicate damage to a frontbumper of the vehicle, and a first calculated estimate may comprise anestimate for repairing the first bumper. A second annotation mayindicate damage to a rear bumper of the vehicle, and a second calculatedestimate may comprise an estimate for repairing the rear bumper. A thirdannotation may indicate damage to a passenger side mirror that has beendeemed unrelated to the incident.

The process may then move to step 4611 where the device displays anaggregated estimate. For example, a device (e.g., server 101, terminal141 and/or terminal 151) may display an aggregated estimate to a user(e.g., claims processor, administrator, and the like). In an embodiment,an aggregated estimate may comprise a first calculated estimateassociated with a first annotation and second calculated estimateassociated with a second annotation, but not a third calculated estimateassociated with a third annotation deemed unrelated to the incident. Forinstance, where the insured item comprises a vehicle, a first annotationmay indicate damage to a front bumper of the vehicle, and a firstcalculated estimate may comprise an estimate for repairing the firstbumper. A second annotation may indicate damage to a rear bumper of thevehicle, and a second calculated estimate may comprise an estimate forrepairing the rear bumper. A third annotation may indicate damage to apassenger side mirror of the vehicle and may have a calculated estimatefor repairing or replacing the side mirror. An aggregated estimate maycomprise the first calculated estimate and the second calculatedestimate, but not the third calculated estimate.

In some aspects of the disclosure, the device implementing the processof FIG. 46 may comprise a multi-touch screen (e.g., a tablet computer)and estimate data may be received from the user via the multi-touchscreen. In some embodiments, the received data may be associated withclaim information. For example, a claim may have been generated for anevent, such as a vehicle accident, and the received data may comprisephotos of a vehicle involved in the accident. The received data may beassociated with generated claim, which may include a customer name, adate for the event, a description for the event, a location for theevent, a location for the customer, a VIN number for the vehicle, apolicy number, and any other suitable claim information. The process ofFIG. 46 may comprise additional steps, may omit described steps, and/ormay be performed in a different order.

FIG. 47 shows a display screen displayed to a user of a device inaccordance with at least one aspect of the present disclosure. Screen4701 shows a damage display screen displayed to a user in accordancewith at least one aspect of the present disclosure. For example, screen4701 may display photo 4701 a, such as a photo about an insured item(e.g., a vehicle). Photo 4701 a may comprise a photo of a vehicle thathas been in an accident and may show damage to the vehicle.

In an embodiment, interface 4705 a may comprise a plurality ofselectable photos. For example, a plurality of photos may be receivedabout an event (e.g., a vehicle accident) or a plurality of photos maybe associated with a claim (e.g., an insurance claim). In this example,the plurality of photos may be displayed within interface 4705 a and oneor more of the plurality of photos may be selected and displayed ondisplay screen 4701. In an embodiment, a user may select a photo with amember, such as finger, by touching the display and dragging the photofrom interface 4705 a.

In an embodiment, photo 4701 a may be adjusted, for example, by a user.For instance, size, zoom, contrast, tint, brightness, gray scale, imagerotation, and any other suitable aspect of photo 4701 a may be adjusted.In this example, a user may adjust these aspects of photo 4701 a using atouch screen display. In an embodiment, aspects for a plurality ofphotos may be adjusted by a user. A user may, for example, view one ormore photos and annotate these displayed photos.

Display screen 4701 may comprise loss facts 4703 a about, for example,an insurance claim. The loss facts may comprise a policy holder name, adate for an event (e.g. an accident), a description for the event, alocation for the event, a location for the policy holder, a VIN numberfor a vehicle involved in the event, a make for the vehicle, a model forthe vehicle, a manufacture year for the vehicle, a policy number, andany other suitable information.

In an embodiment, a damage annotation may be received that is associatedwith one or more photos. For example, a user may input a damageannotation with a member, such as finger, by touching the display. FIG.48 shows a display screen displayed to a user of a device in accordancewith at least one aspect of the present disclosure. Screen 4801 shows adamage display screen displayed to a user in accordance with at leastone aspect of the present disclosure. For example, screen 4801 maydisplay photo 4801 a, such as a photo about an insured item (e.g., avehicle). In an embodiment, a user may touch the display in order toinput a damage annotation. In an example where the user has touched thedisplay in order to input damage annotation 4803 a, interface 4805 a maybe associated with damage annotation 4803 a and interface 4805 a mayfurther receive estimate data about the damage annotation.

Interface 4805 a may comprise input field 4805 b, where a part locationmay be input. For example, damage annotation 4803 a may be located atthe front of a vehicle, and input field 4805 b may receive this locationinformation. Interface 4805 a may further comprise input field 4805 c,where a part description may be input. For example, a user may determinethat the damage is related to a part, such as a front fender of avehicle, and input field 4805 c may receive this part description.Interface 4805 a may further comprise input field 4805 d, where a laborduration may be input. For example, a user may estimate the labor forrepairing the damage indicated by annotation 4803 a (e.g., hours oflabor) and may input the labor duration into input field 4805 d.

In some embodiments, a claim may have been generated for an event, suchas a vehicle accident, and photo 4801 a and damage annotation 4803 a maybe associated with the generated claim. The claim information mayinclude a customer name, a date for the event, a description for theevent, a location for the event, a location for the customer, a VINnumber for the vehicle, a policy number, and any other suitable claiminformation.

In some aspects of the disclosure, a device displaying screen 4805(e.g., server 101, terminal 141 and/or terminal 151) may be operativelyconnected to a database (e.g., database 121). The database may storepart information for makes and models for a plurality of cars. In anembodiment, the database may additionally store cost information for oneor more parts, such as the cost for repairing a part and the cost forreplacing a part. For example, the database may store part information,such as a fender type, for a car of a first make and a first model, andthe cost for repairing the fender and the cost for replacing the fender.The cost stored in the database may comprise a cost for parts, parts andlabor, or any other suitable cost.

In some embodiments, based on the claim information or the loss facts,one or more of input fields 4805 b and 4805 c may be prepopulated. Forexample, a make and model for the vehicle associated with the claim maybe determined based on the claim information or loss facts, and thedatabase may be queried to determine part information for the make andmodel. Input fields 4805 b and 4805 c may comprise drop down menus, andthe drop down menus may be prepopulated based on the make and model ofthe vehicle involved in the claim. In an example, a vehicle may be of afirst make and model, part information may be determined for thevehicle, and this part information may be prepopulated in a drop downmenu that comprises input field 4805 c.

In an embodiment, interface 4805 d may be used to input a labor typealong with a labor duration. For example, when the damage comprises adented fender, the labor type may comprise body work. In anotherexample, the labor type may comprise engine work or any other suitabletype of labor type.

In an embodiment, estimate data may be input for a damage annotation andthe estimate data may be displayed to a user. FIG. 49 shows a displayscreen displayed to a user of a device in accordance with at least oneaspect of the present disclosure. Screen 4901 shows an estimate displayscreen displayed to a user in accordance with at least one aspect of thepresent disclosure. For example, screen 4901 may display photo 4901 a,such as a photo about an insured item (e.g., a vehicle). In anembodiment, annotation 4903 a may comprise a damage annotation thatindicates damage displayed at a portion of the photo. In an example,estimate data may be received about damage annotation 4903 a inaccordance with some aspects of the present disclosure.

In an embodiment, an estimate for damage annotation 4903 a may becalculated, and the estimate may be displayed at user interface element4905 a. For example, the received estimate data associated with damageannotation 4903 a may indicate repair costs for a front fender of thevehicle involved the accident. The estimate may include a replacementcost for the parts (e.g., fender and paint) and labor (e.g.,installation and painting). A total for the estimate may further bedisplayed.

In some aspects of the disclosure, the cost for parts and/or labor maybe queried from a database based on associated claim information, asfurther described above. For example, based on the make, model, and/oryear of manufacture for a vehicle, a cost may be determined for areplacement front fender based on stored cost information. A labor costmay be calculated using a labor duration (e.g. number of hours) and ratebased on a received labor type (e.g., body work, engine work, and thelike). For example, a rate for engine work may be more expensive that arate for body work.

In an embodiment, estimate data may be input for a plurality of damageannotations and the estimate data may be displayed to a user. Forexample, the damage annotation 4903 a may be associated with one or morephotos and may indicate damage to a front fender of a vehicle. In anembodiment, a second damage annotation may be input that is associatedwith one or more photos and that indicates damage to, for example, arear fender of the vehicle. FIG. 50 shows a display screen displayed toa user of a device in accordance with at least one aspect of the presentdisclosure. Screen 5001 shows an estimate display screen with aplurality of estimates displayed to a user in accordance with at leastone aspect of the present disclosure. For example, screen 5001 maydisplay photo 5001 a, such as a photo about an insured item (e.g., avehicle). Photo 5001 a may be related to photo 4901 a such that thephotos are part of a set of photos received in association with an event(e.g. a vehicle accident), an insurance claim, or any other suitableassociation. Damage annotation 5003 a may comprise a damage annotationthat indicates damage displayed at a portion of photo 5001 a, such as arear fender. In an example, estimate data may be received about damageannotation 5003 a similar to the manner described above with referenceto damage annotation 4903 a and an estimate for damage annotation 5003 amay be calculated similar to the manner described above with referenceto damage annotation 4903 a. In some aspects, an annotation may be inputto indicate damage to an insured item that is unrelated to a particularaccident. For example, a user may input an annotation indicating damageto a side mirror of a vehicle after the vehicle was damaged in anaccident.

Accordingly, damage annotation 4903 a may be associated with photo 4901a and may indicate damage to a front fender of a vehicle and damageannotation 5003 a may be associated with photo 5001 a and may indicatedamage to a back fender of a vehicle. In this example, user interfaceelement 5005 a may display estimate data for damage annotation 4901 aand damage annotation 5003 a. For instance, user interface element 5005a may comprise user interface element 5005 b that displays estimate datafor damage annotation 4903 a and user interface element 5005 c thatdisplays estimate data for damage annotation 5003 a. The estimate datamay be selected for display or not for display by selecting userinterface elements 5005 b and 5005 c, such as by touching the displaywith a member (e.g., a finger). The user may then also input that thedamage to the side mirror is unrelated to the accident, or in someaspects, server 101 may recognize that the damage to the side mirror isunrelated to the accident (e.g., based on the loss facts). In certainaspects, unrelated damage to the insured item may or may not have anestimate associated with it.

In an embodiment, when a user interface element associated with a damageannotation is selected (e.g. selected for display), the one or morephotos associated with the damage annotation are displayed. For example,in FIG. 50 user interface element 5005C is selected for display. Userinterface element 5005 c displays estimate data for damage annotation5003 a. Accordingly, and based on the selection, photo 5001 a isdisplayed because photo 5001 a is associated with damage annotation 5003a. In some aspects of the disclosure, one or more photos associated witha damage annotation are automatically displayed when the user interfaceelement associated with the damage annotation is selected (e.g. selectfor display).

In an embodiment, multiple user interface elements may be selected fordisplay. FIG. 51 shows a display screen displayed to a user of a devicein accordance with at least one aspect of the present disclosure. Screen5101 shows an estimate display screen with a plurality of estimatesdisplayed to a user in accordance with at least one aspect of thepresent disclosure. For example, screen 5101 may display photos 5001 aand 5001 b. Photo 5101 a may be similar to photo 4901 a and photo 5101 bmay be similar to photo 5001 a. Photo 5101 a may be related to photo5101 b such that the photos are part of a set of photos received inassociation with an event (e.g. a vehicle accident), an insurance claim,or any other suitable association. Photo 5101 a may display damage to afront fender of a vehicle and photo 5101 b may display damage to a backfender of the vehicle.

Damage annotation 5103 a may comprise a damage annotation that indicatesdamage displayed at a portion of photo 5001 a, such as a front fender,and damage annotation 5103 b may comprise a damage annotation thatindicates damage displayed at a portion of photo 5101 b, such as a rearfender. Damage annotation 5103 a may be similar to damage annotation4903 a and damage annotation 5103 b may be similar to damage annotation5003 a. User interface element 5105 a may display estimate data fordamage annotation 5103 a and damage annotation 5103 b. For instance,user interface element 5105 a may comprise user interface element 5105 bthat displays estimate data for damage annotation 5103 a and userinterface element 5005 c that displays estimate data for damageannotation 5103 b. In an embodiment, a total for estimates for bothdamage annotations may be displayed. The estimate data may be selectedfor display or not for display by selecting user interface elements 5105b and 5105 c, such as by touching the display with a member (e.g., afinger). Furthermore, damage annotation may comprise annotationsindicating damage unrelated to a particular accident (e.g., unrelateddamage). Damage annotation may also comprise comments about an area inquestion that may require further examination (e.g., providing commentsthat may aid an expert with inspection of the damaged item).

For example, in FIG. 51 user interface element 5105 b and 5105 c areselected for display. User interface element 5105 b displays estimatedata for damage annotation 5103 a and User interface element 5105 bdisplays estimate data for damage annotation 5103 b. Based on theselection for displaying both user interface elements, photos 5101 a and5101 b are displayed because photo 5101 a is associated with damageannotation 5103 a and because photo 5101 b is associated with damageannotation 5103 b.

In an embodiment, a damage annotation may be associated with a pluralityof photos. FIG. 52 shows a display screen displayed to a user of adevice in accordance with at least one aspect of the present disclosure.Screen 5201 shows an estimate display screen with a plurality ofestimates displayed to a user in accordance with at least one aspect ofthe present disclosure. For example, screen 5201 may display photos 5201a and 5201 b. Photo 5201 a may be related to photo 5201 b such that thephotos are part of a set of photos received in association with an event(e.g. a vehicle accident), an insurance claim, or any other suitableassociation. Photos 5201 a and 5201 b may display damage to a frontfender of a vehicle, but may do so in a different ways (e.g., fromdifferent angles, vantage points, zoom levels, and the like).

In an embodiment, a damage annotation 5203 a may indicate damage to afront fender of the vehicle and may be associated with photo 5201 a.Estimate data may be received for damage annotation 5203 a in a similarmanner as described above. In an example, damage annotation 5203 b mayalso indicate damage to a front fender of the vehicle and may beassociated with photo 5201 b. Accordingly, damage annotation 5203 a and5203 b may be linked. For instance, damage annotation 5203 b may beinput as a clone or replica of damage annotation 5203 a.

In an embodiment, photos 5201 a and 5201 b may be grouped together basedon the photos displaying damage to the same portion of the vehicle. Forexample, a user may link photos 5201 a and 5201 b by selecting bothphotos and indicating that they are linked. In another example, photos5201 a and 5201 b may be linked based on damage annotations 5203 a and5203 b. It may be determined that damage annotations 5203 a and 5203 bare linked, or that one damage annotation is a clone or replica of theother. Accordingly, photos 5201 a and 5201 b may be linked becausephotos 5201 a is associated with damage annotation 5203 a and photo 5201b is associated with damage annotation 5203 b.

In an embodiment, user interface element 5205 a may display estimatedata for damage annotation 5203 a and damage annotation 5203 b. Forinstance, user interface element 5205 a may comprise user interfaceelement 5205 b that displays estimate data for damage annotations 5203 aand 5203 b. In an example, user interface element 5205 b may displayestimate data for both damage annotations 5203 a and 5203 b because thedamage annotations are linked. For instance, user interface element 5205b may display estimate data from a cost for repairing a front bumper fora damaged vehicle. Because damage annotations 5203 a and 5203 b are bothrelated to damage to the front bumper of the vehicle, user interfaceelement 5205 b may display estimate data from both damage annotations.The estimate data may be selected for display or not for display byselecting user interface element 5205 b, such as by touching the displaywith a member (e.g., a finger).

In an embodiment, when a user interface element associated with a damageannotation is selected (e.g. selected for display), the one or morephotos associated with the damage annotation are displayed. For example,in FIG. 52 user interface element 5205 b is selected for display. Basedon the selection the user interface element, photos 5201 a and 5201 bare displayed. In an embodiment, photos 5201 a and 5201 b are displayedbecause photo 5201 a is associated with damage annotation 5203 a andbecause photo 5201 b is associated with damage annotation 5203 b. Inanother embodiment, photos 5201 a and 5201 b may both be displayedbecause one of these photos has been displayed and the photos havepreviously been grouped or linked.

It should be noted that one or more aspects of the above-describedembodiments may be applied to various types of items that may or may notbe insured, such as vehicles, homes, other properties, etc.

The foregoing descriptions of the disclosure have been presented forpurposes of illustration and description. They are not exhaustive and donot limit the disclosure to the precise form disclosed. Modificationsand variations are possible in light of the above teachings or may beacquired from practicing of the disclosure. For example, the describedimplementation includes software but the present disclosure may beimplemented as a combination of hardware and software or in hardwarealone. Additionally, although aspects of the present disclosure aredescribed as being stored in memory, one skilled in the art willappreciate that these aspects can also be stored on other types ofcomputer-readable media, such as secondary storage devices, like harddisks, floppy disks, or CD-ROM; a carrier wave from the Internet orother propagation medium; or other forms of RAM or ROM.

1. A method, comprising: obtaining, by a mobile computing device,instruction data indicating a damaged portion of an item; obtaining, bythe mobile computing device, an indication of a perspective view of thedamaged portion of the item, wherein the perspective view corresponds tothe instruction data; generating, by the mobile computing device, agraphical visual aid based on the instruction data and the indication ofthe perspective view, the graphical visual aid comprising at least onevisual marker indicating a positioning of the mobile computing devicerelative to the damaged portion of the item according to the indicatedperspective view; displaying, by the mobile computing device, a view ofthe item and the graphical visual aid; capturing, by the mobilecomputing device and when the mobile computing device is in the positionrelative to the damaged portion of the item indicated by the graphicalvisual aid based on the indicated perspective view, an image of thedamaged portion of the item indicated in the instruction data;transmitting, by the mobile computing device, the image; receiving, bythe mobile computing device, information generated based on the imageand associated with the item; receiving, by the mobile computing device,input data indicating a request to view the information associated withthe item; and displaying, by the mobile computing device and in responseto the input data, the information.
 2. The method of claim 1, furthercomprising: receiving, by the mobile computing device, notification dataindicating that the image is not acceptable; and displaying, by themobile computing device, a notification generated based on thenotification data.
 3. The method of claim 2, further comprising:displaying, by the mobile computing device, a second graphical visualaid comprising at least one second visual marker indicating apositioning of the mobile computing device relative to the item;capturing, by the mobile computing device and when the mobile computingdevice is in the position indicated by the second graphical visual aid,a second image of the damaged portion of the item indicated in thenotification data; and transmitting, by the mobile computing device, thesecond image.
 4. The method of claim 2, wherein the notification dataindicates that the image is blurry.
 5. The method of claim 1, furthercomprising determining, by the mobile computing device, that the imagefails to meet at least one quality criteria.
 6. The method of claim 5,wherein the at least one quality criteria comprises a quality criterionrelated to blurriness.
 7. The method of claim 1, further comprisingdisplaying, by the mobile computing device, thumbnail images of imagescaptured by the mobile computing device.
 8. A mobile computing device,comprising: one or more processors; and memory storing instructionsthat, when executed by the one or more processors, cause the mobilecomputing device to: obtain instruction data indicating a damagedportion of an item; obtaining an indication of a perspective view of thedamaged portion of the item, wherein the perspective view corresponds tothe instruction data; generate a graphical visual aid based on theinstruction data and the indication of the perspective view, thegraphical visual aid comprising at least one visual marker indicating apositioning of the mobile computing device relative to the damagedportion of the item according to the indicated perspective view; displaya view of the item and the graphical visual aid; capture, when themobile computing device is in the position relative to the damagedportion of the item indicated by the graphical visual aid based on theindicated perspective view, an image of the damaged portion of the itemindicated in the instruction data; transmit the image; receiveinformation generated based on the image and related to the item;receive input data indicating a request to view information associatedwith the item; and display, in response to the input data, theinformation.
 9. The mobile computing device of claim 8, wherein theinstructions that, when executed by the one or more processors, furthercause the mobile computing device to: receive notification dataindicating that the image is not acceptable; and display a notificationgenerated based on the notification data.
 10. The mobile computingdevice of claim 9, wherein the instructions that, when executed by theone or more processors, further cause the mobile computing device to:display a second graphical visual aid comprising at least one secondvisual marker indicating a positioning of the mobile computing devicerelative to the item; capture, when the mobile computing device is inthe position indicated by the second graphical visual aid, a secondimage of the damaged portion of the item indicated in the notificationdata; and transmit the second image.
 11. The mobile computing device ofclaim 9, wherein the notification data indicates that the image isblurry.
 12. The mobile computing device of claim 8, wherein theinstructions that, when executed by the one or more processors, furthercause the mobile computing device to determine that the image fails tomeet at least one quality criteria.
 13. The mobile computing device ofclaim 12, wherein the at least one quality criteria comprises a qualitycriterion related to blurriness.
 14. The mobile computing device ofclaim 8, wherein the instructions that, when executed by the one or moreprocessors, further cause the mobile computing device to displaythumbnail images of images captured by the mobile computing devicerelated to the item.
 15. A non-transitory machine-readable mediumstoring instructions that, when executed by one or more processors,cause the one or more processors to perform steps via a mobile computingdevice, the steps comprising: obtaining instruction data indicating adamaged portion of an item; obtaining an indication of a perspectiveview of the damaged portion of the item, wherein the perspective viewcorresponds to the instruction data; generating a graphical visual aidbased on the instruction data and the indication of the perspectiveview, the graphical visual aid comprising at least one visual markerindicating a positioning relative to the damaged portion of the item andaccording to the indicated perspective view; displaying a view of theitem and the graphical visual aid; capturing, when the mobile computingdevice is in the position relative to the damaged portion of the itemindicated by the graphical visual aid based on the indicated perspectiveview and the at least one visual marker, an image of the damaged portionof the item indicated in the instruction data; transmitting the image;receiving information s generated based on the image and associated withthe item; receiving input data indicating a request to view informationassociated with the item; and displaying, in response to the input data,the information.
 16. The non-transitory machine-readable medium of claim15, wherein the instructions that, when executed by one or moreprocessors, further cause the one or more processors to perform stepscomprising: receiving notification data indicating that the image is notacceptable; and displaying a notification generated based on thenotification data.
 17. The non-transitory machine-readable medium ofclaim 16, wherein the instructions that, when executed by one or moreprocessors, further cause the one or more processors to perform stepscomprising: displaying a second graphical visual aid comprising at leastone second visual marker indicating a positioning of a computing devicerelative to the item; capturing, based on the display of the item and aposition indicated by the second graphical visual aid, a second image ofthe damaged portion of the item indicated in the notification data; andtransmitting the second image.
 18. The non-transitory machine-readablemedium of claim 16, wherein the notification data indicates that theimage is blurry.
 19. The non-transitory machine-readable medium of claim15, wherein the instructions that, when executed by one or moreprocessors, further cause the one or more processors to perform stepscomprising determining that the image fails to meet at least one qualitycriteria.
 20. The non-transitory machine-readable medium of claim 19,wherein the at least one quality criteria comprises a quality criterionrelated to blurriness.